Systems and methods for integrating web platforms with mobile device operations

ABSTRACT

A system for managing a financial account in a low cash mode. The system may include a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include providing an interface; providing a notification to a user when a balance in the first account is deemed to be in low cash mode; presenting, when the first account balance is deemed to be in low cash mode, an option for a transfer request; receiving, a selection of the option for the transfer request to connect the first account with a second account; transferring funds from the second account to the first account; notifying the user that funds have been transferred from the second account to the first account; and further notifying the user that the balance in the first account is greater than the threshold value.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.17/027,250, filed Sep. 21, 2020, which claims priority to ProvisionalU.S. Patent Application Ser. No. 62/983,572, filed Feb. 28, 2020, thedisclosures of which are incorporated herein by reference.

TECHNICAL FIELD

The disclosed embodiments relate to systems and methods for providingfinancial services, more particularly, providing customers the optionsto manage their financial accounts when their account balance is low,and additionally, to an application that provides comprehensivetransactional services for customers managing their financial accountsin a low cash mode.

BACKGROUND

Financial service providers are rapidly expanding the use of mobileservices and mobile applications. Currently, most financial serviceproviders provide mobile banking services which allow customers toperform basic functions and transactions remotely, for example, by usingan application on a mobile device such as a cell phone or a tablethaving an online web interface. Mobile banking allows customers tomanage their money without visiting a physical brick and mortar branchbank location. Customers may check account balances, pay bills, transferfunds, send money to others, deposit checks, receive customer support,apply for loans, receive alerts, apply for credit cards, managebenefits, manage credit/debit cards, review transactions, open newaccounts, and perform many other banking services on a mobileapplication on a mobile device without travelling to a physicallocation. The financial services providers provide these functions tocustomers electronically via an application without the need forin-person teller services.

While these banking functions are useful for enabling funds to beelectronically transferred without the need for paper checks or tellersupport, they are limited to certain transactions. Moreover, theseexemplary banking functions are further limited when a user orcustomer's account balance is low or falls beneath a predeterminedthreshold dollar value (e.g. $25). As a result, what is needed is anonline banking application that provides customers the ability to managetheir financial accounts and perform banking operations when theiraccount balance is low. In particular, what is needed is a mobilebanking application that provides options for a user operating in a lowcash mode, provides alerts to customers when they enter low cash mode,and prevents overdraft once a low cash mode is reached. Additionally,what is needed are preventive options, such as providing personal loans,transferring funds, facilitating automatic and manual transfers,cancelling transactions including cancellation of pending AutomatedClearing House (“ACH”) (or pending checks that will generate theoverdraft(s)), and accelerating pending ACH/payroll deposits.

Furthermore, what is needed is a mobile application that provides tieredoverdraft fees based on the extent to which an account is negative,incorporates synthetic data and machine learning into an ACH andanalytics, provides mobile network transfers (for added dataprotection), incorporates machine learning algorithms for learningcustomer transaction tendencies, provides fraud protection features in amobile application specifically relating to the issues of a low cashmode and/or overdraft scenario, and integrates a low cash mode into aseparate virtual wallet application. What is needed is a link between acustomer's virtual wallet and a customer's social media (such as, aFacebook account), providing a notification channel to customers inorder to provide an alert that a purchase will overdraft an accountbefore a purchase is made while a customer's account is in low cashmode. What is needed is an overall increase in efficiency in providingfinancial services through automation, including, for example, throughautomated balance confirmation.

Moreover, what is needed is a mobile application that provides anautomatic card lock feature that activates automatically when an accountenters low cash mode with an option that allows a user to turn offwithin the application. What is further needed is an automatic card lockfeature that activates automatically when an account enters a low cashmode based on a predicted balance (e.g., a payment or direct depositscheduled for tomorrow) as well as based on a customer's currentbalance. What is needed is the ability for a customer to select andswitch between overdraft protection features (e.g., pay, cancel,protection through loans or transfers and accelerated ACH/payrolldeposits) on a mobile application without the need for bankintervention. What is needed is a mobile application that providescustomers the option to pay some, but not all, transactions that wouldoverdraft an account (such an application would also facilitate thecustomer's ability to prioritize transactions and potentially delay thepayment of some transactions and would differentiate point of saletransactions from ACH transactions, checks, and scheduled payments).

Additionally, what is needed is a mobile application that enables acustomer to approve or deny spending for an entire day while an accountis in low cash mode or while a card lock feature is activated, a mobileapplication that provides an alert notifying a customer of the abilityto approve or deny spending for a day, and that provides an alert for acustomer to configure how an account can spend for the day. Further,what is needed is a mobile application that provides a debit card smartlock feature, with a threshold that may be different from a low cashmode threshold and that can be disabled in a mobile application, thatautomatically prevents a customer from using the locked card when acustomer's balance falls below a set threshold value, and allows acustomer to manually or automatically draw funds from a second accountwhen a first account has insufficient funds.

Furthermore, what is needed is a feature that allows a user to blockcertain mobile application functionality from a web application when acustomer's phone is lost or stolen. Further, what is needed is a mobileapplication that displays the amount of (specified) time a customer hasto cure an overdraft (such as a grace period), which may help customerswho otherwise don't handle money or time well to remember to cure anoverdraft, that notifies a customer at predetermined times during anoverdraft grace period using push notifications to a user's phone ormessages to the user, which may also help customers remember to cure anoverdraft, and that personalizes a grace period based on customercharacteristics.

What is needed are personalizing characteristics that may includeoffering a customer more or less time for larger or smaller overdraftamounts, offering a customer a longer grace period if their balance isordinarily high, offering a customer a longer grace period if a customeris in good standing with a bank, as indicated, for example, by moredebit card use, higher average balance, or higher direct deposits.Personalizing characteristics that are needed may also include extendinga grace period if a customer makes a payment for less than an overdraftfee, offering a customer a fixed amount of overdraft time per month thatmay be spread over the month, or offering a customer a longer or shortergrace period over time. If, for example, a customer overdrafts once witha grace period of 48 hours, the next overdraft may have a grace periodof 24 hours. If, for example, a customer does not overdraft for severalmonths, a customer may earn additional grace period time. Personalizingcharacteristics that are needed may further include carrying acustomer's extra grace period time over from month to month, with a capon the total overdraft time available, giving customers a bucket ofaccrued grace period time that they can add to their current graceperiod to cash out the accrued time, offering a customer a grace periodas a reward/relationship benefit as a part of a package, and/or sellinga customer additional grace period time by which to cure a negativebalance.

Furthermore, what is needed is a mobile application that allows acustomer to dynamically set reminders to make a scheduled payment lateror to set a reminder to make the payment later, that updates otherapplications, focusing on the ability to automatically reschedulepayments on behalf/invocation of a virtual wallet calendar, that chargesa customer a negative balance fee instead of a transactional/per itemfee for insufficient funds, that recommends cancelling particularscheduled payments but proceeding with others in a way thatminimizes/prevents overdraft or prevents other fees, and that prevents agiven customer's balance to drop below a given tolerance value byallowing a customer to choose certain scheduled payments to process andrendering the remaining payments no longer actionable.

Moreover, what is needed is a mobile application that provides apredictive cash flow feature, which uses machine learning to predict acustomer's expenses and alerts a customer to potential periods duringwhich a customer will have a low or negative balance, and a predictivecash mode feature that allows a customer to manually add paymentsflagged by a predictive cash mode to help prevent a low or negativebalance. What is also needed is a mobile application that links acustomer's account to social media to facilitate communication with acustomer by, for example, sending a message to a customer throughFacebook Messenger, that uses geolocation technology to alert a customerwho is entering a store that the customer's account is in low cash mode,that provides a feature to include spouses or joint users, so that ajoint user on a customer's account is also notified when another jointuser arrives at a geographic location, such as a store while theassociated account is in low cash mode, that turns on this feature at apredicted danger day or at particular high-risk stores for thecustomers, and that obtains the customer's consent for the use of thisfeature.

Finally, what is needed is a mobile application that allows a user todesignate particular transactions or locations to process even while ina low cash mode (for example, a customer may want the ability to buygroceries, even while in low cash mode), and that provides auser-friendly graphical user interface of a low cash mode feature.

SUMMARY

One aspect of the present disclosure is directed to a system formanaging a financial account in a low cash mode. The system may includeat least one processor; and at least one memory configured to executethe instructions to perform operations. The operations may includeproviding an interface accessible via a user device registered with afirst account; providing, via the interface, a notification to a userwhen a balance in the first account is less than a threshold value;presenting, when the first account balance is less than a thresholdvalue, an option for a transfer request; receiving, via the interface, aselection of the option for the transfer request to connect the firstaccount with a second account; transferring cash, based on the request,from the second account to the first account; notifying, via theinterface, the user that cash has been transferred from the secondaccount to the first account; and further notifying, via the interface,the user that the balance in the first account is greater than thethreshold value.

Another aspect of the present disclosure is directed to a method formanaging a financial account in a low cash mode. The method may performoperations including providing an interface accessible via a user deviceregistered with a first account; providing, via the interface, anotification to a user when a balance in the first account is less thana threshold value; presenting, when the first account balance is lessthan a threshold value, an option for a transfer request; receiving, viathe interface, a selection of the option for the transfer request toconnect the first account with a second account; transferring cash,based on the request, from the second account to the first account;notifying, via the interface, the user that cash has been transferredfrom the second account to the first account; and further notifying, viathe interface, the user that the balance in the first account is greaterthan the threshold value.

Yet another aspect of the present disclosure is directed to anon-transitory computer-readable medium. The non-transitory computerreadable medium may perform a method for managing a financial account ina low cash mode. The method may perform operations including providingan interface accessible via a user device registered with a firstaccount; providing, via the interface, a notification to a user when abalance in the first account is less than a threshold value; presenting,when the first account balance is less than a threshold value, an optionfor a transfer request; receiving, via the interface, a selection of theoption for the transfer request to connect the first account with asecond account; transferring cash, based on the request, from the secondaccount to the first account; notifying, via the interface, the userthat cash has been transferred from the second account to the firstaccount; and further notifying, via the interface, the user that thebalance in the first account is greater than the threshold value.

Aspects of the present disclosure may include systems, methods, andcomputer readable media for providing notifications to a customer, theoperations comprising associating the customer with an account,associating the account with a mobile device, determining an accountbalance of the account, and determining, based on the account balance,whether the account is deemed to be in a low cash mode state. Theoperations may further comprise providing, via the mobile device, anotification to the customer when the account enters the low-cash modestate and providing, via the mobile device, a notification to thecustomer when the account enters the low-cash mode state.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing an account fromentering a low cash mode state, the operations comprising associatingthe customer with an account, associating the account with a mobiledevice, determining an account balance of the account, and determining,based on the account balance, whether the account is deemed to be in alow cash mode state. The operations may further comprise providing, viathe mobile device, a notification to the customer when the accountenters the low-cash mode state and providing, via the mobile device, anotification to the customer when the account enters the low-cash modestate.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing an account fromentering a low cash mode state, the operations comprising associatingthe customer with an account, associating the account with a mobiledevice, determining an account balance of the account, and predicting,as a result of an initiated transaction, that the initiated transactionwill result in the first account entering the low cash mode state. Theoperations may further comprise providing, via the mobile device, anotification to the customer when the account is predicted to enter thelow-cash mode state and presenting, with the notification, options tothe customer to manage the first account while the first account ispredicted to enter the low cash mode state.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing an account fromentering a low cash mode state, the operations comprising associating acustomer with a first account, associating the customer with a secondaccount, linking the second account with the first account, determininga first account balance of the first account, and determining, based onthe first account balance, whether the first account is deemed to be inthe low cash mode state. The operations may further comprisetransferring, automatically, when the first account is deemed to be inthe low cash mode state, funds from the second account into the firstaccount, processing the initiated transaction, and presenting anotification to the customer.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for determining a negative balancefee, the operations comprising associating a customer with a firstaccount, determining a first account balance of the first account, andassessing, when the first account balance is negative, the negativebalance fee.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for generating synthetic data, theoperations comprising associating a customer with an account, storingdata associated with the account, applying machine learning to the datato generate synthetic field-level data, and substituting the syntheticfield-level data in place of field-level data associated with theaccount in an Automated Clearing House transaction or a mobile networktransfer.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for analyzing historical data, theoperations comprising associating a customer with an account, storingdata associated with the account, applying machine learning to the datato determine transaction tendencies, and using the transactiontendencies to predict an account balance.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for presenting and using accountmanagement options, the operations comprising associating a customerwith an account, providing options for managing the account, andimplementing the selected options.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for integrating social media andfinancial services, the operations comprising associating a customerwith a first account at a financial institution, associating thecustomer with a social media account, linking the first account with thesocial media account, determining a first account balance of the firstaccount, determining, based on the first account balance, whether thefirst account is deemed to be in a low cash mode state, and providing anotification to the customer when the first account is deemed to be inthe low cash state.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for integrating social media andfinancial services the operations comprising associating a customer witha first account at a financial institution, associating the customerwith a social media account, presenting an option for the customer togrant the financial institution permission to link the first account andthe social media account, receiving permission to link the first accountand the social media account, receiving permission to link the firstaccount and the social media account, and linking the first account withthe social media account. The operations may further comprisedetermining a first account balance of the first account, determining,based on the first account balance, whether the first account is deemedto be in a low cash mode state, and providing a notification to thecustomer when the first account is deemed to be in the low cash modestate using the social media account.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing a negative accountbalance, the operations comprising associating a customer with anaccount at a financial institution, associating the account with amobile device, determining a first account balance of the first account,determining, based on the first account balance, whether the firstaccount is deemed to be in a low cash mode state, identifying apotential purchase and a potential purchase amount, determining, basedon the potential purchase amount and the first account balance, whetherthe potential purchase will result in a negative first account balance,providing a notification to the customer that the potential purchasewill result in a negative first account balance.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing a negative accountbalance, the operations comprising associating a customer with anaccount at a financial institution, associating a customer with anaccount at a financial institution, determining a first account balanceof the first account, determining, based on the first account balance,whether the first account is deemed to be in a low cash mode state,receiving a request for transfer of funds from a transaction initiatedby the card, and denying the request for monetary transfer while thefirst account is deemed to be in the low cash mode state.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for predicting low-cash mode state,the operations comprising associating a customer with a first account,storing financial history data associated with the customer, accessingnon-financial data, analyzing the financial history data and thenon-financial data, determining, a future account balance of the firstaccount, based on scheduled transactions, the financial history data,and the non-financial data, and determining whether the first account isdeemed to be in the low-cash mode state based on the future accountbalance.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for avoiding negative accountbalance, the operations comprising providing an interface accessible viaa user device associated with a first account, associating a customerwith the first account at a financial institution, determining a firstaccount balance of the first account, determining, based on the firstaccount balance, whether the first account is less than a thresholdvalue, providing, via the interface, a notification to the customer whenthe first account balance is less than the threshold value, andproviding, via the interface, a notification to the customer when thefirst account balance is less than the threshold value.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for avoiding negative accountbalance, the operations comprising associating a customer with a firstaccount, determining a first account balance of the first account,determining, based on the first account balance, whether the firstaccount is deemed to be in a low cash mode state, providing anotification to the customer when the first account is deemed to be inthe low cash mode state, and presenting, with the notification, optionsto the customer to manage the first account while the first account isdeemed to be in the low cash mode state.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for managing accounts, theoperations comprising associating a customer with an account,determining an account balance of the account, determining, based on theaccount balance, whether the account is deemed to be in a low cash modestate, determining whether smart lock is activated, providing a firstnotification to the customer when the account is deemed to be in the lowcash mode state, providing a second notification to the customer whensmart lock is activated, and presenting, with the first notification, atleast one option to the customer to manage the first account.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for managing accounts, theoperations comprising associating a customer with an account,associating a card with the account, determining whether smart lock isactivated, receiving a request to transfer funds from a transactioninitiated by the card, and denying, when smart lock is activated, therequest.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing fraudulenttransactions, the operations comprising associating a customer with anaccount, associating the account with a mobile device, receiving arequest to disable a function in an application on the mobile device,and processing the request.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for managing a negative accountbalance, the operations comprising associating a customer with anaccount, determining an account balance of the account, determining,based on the account balance, whether the account balance is negative,and displaying a time remaining until a negative balance fee isassessed.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for managing a negative accountbalance, the operations comprising associating a customer with anaccount, determining an account balance of the account, determining,based on the account balance, whether the account balance is negative,providing a first notification to the customer when the account balanceis negative, and providing, after a specific amount of time, a secondnotification to the customer when the account balance is negative.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for generating a personalized graceperiod, the operations comprising associating a customer with an accountat a financial institution, determining an account balance of theaccount, determining, based on the account balance, whether the accountbalance is negative, providing a first notification to the customer whenthe account balance is negative, determining the personalized graceperiod, and displaying, the personalized grace period to the customer.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for providing remindernotifications to a customer, the operations comprising associating acustomer with an account at a financial institution, determining anaccount balance of the account, determining, based on the accountbalance, whether the account balance is negative, providing a firstnotification to the customer when the account balance is negative, andproviding an option for the customer to receive a second notificationwhile the account balance remains negative.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for calendar-based transactionmanagement, the operations comprising associating a customer with anaccount at a financial institution, providing a calendar-based interfacefor the account, wherein a transaction is represented by a location on acalendar corresponding to a date associated with the transaction,assigning a date for processing the transaction based on the location ofthe representation on the calendar, changing the date for processing thetransaction in response to receiving customer input moving therepresentation of the transaction on the calendar, and processing thetransaction on the date for processing the transaction.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for determining a negative balancefee, the operations comprising associating a customer with a firstaccount, determining a first account balance of the first account, andassessing, once during a period of time when the first account balanceis negative, the negative balance fee.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for providing recommendations formanaging an account in a low-cash mode state, the operations comprisingassociating a customer with an account at a financial institution,determining an account balance of the account, storing financial historydata associated with the customer, accessing non-financial data,analyzing the financial history data and the non-financial data,determining, a future account balance of the account, based on theaccount balance, scheduled transactions, the financial history data, andthe non-financial data, and determining whether the first account isdeemed to be in the low-cash mode state based on the future accountbalance.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for maintaining an account above alow balance threshold, the operations comprising associating a customerwith an account at a financial institution, receiving the low balancethreshold from the customer, determining an account balance of theaccount, determining, based on the account balance, whether the accountbalance is less than the low balance threshold, providing a notificationto the customer when the account balance is deemed to be less than thelow balance threshold, and presenting, with the notification, options tothe customer to manage the account while the account balance is lessthan the low balance threshold.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for predicting cash flow, theoperations comprising associating a customer with an account at afinancial institution, storing financial history data associated withthe customer, storing account history data associated with the account,storing aggregated data associated with other customers and otheraccounts, accessing non-financial data, analyzing by machine learningthe financial history data, the account history data, the aggregateddata, and the non-financial data, and determining a future accountbalance of the account, based on scheduled transactions, the financialhistory data, the account history data, the aggregated data, and thenon-financial data. The operations may further comprise determiningwhether the first account is deemed to be in the low-cash mode statebased on the future account balance and determining a danger time periodassociated with the future account balance and the low cash mode state.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing a negative accountbalance, the operations comprising associating a first customer with anaccount at a financial institution, associating a second customer withthe account, associating the first customer with a mobile device,determining an account balance of the account, and determining, based onthe account balance, whether the account is deemed to be in a low cashmode state. The operations may further comprise determining, via themobile device, a location of the first customer, determining if thelocation of the first customer is associated with a location of amerchant, and providing, when the location of the first customer isassociated with the location of a merchant and the account is deemed tobe in the low cash mode state, a notification to the first customer andthe second customer.

Aspects of the present disclosure may additionally include systems,methods, and computer readable media for preventing a negative accountbalance, the operations comprising associating a customer with anaccount at a financial institution, determining an account balance ofthe account, determining, based on the account balance, whether theaccount is deemed to be in a low cash mode state, activating, when theaccount is deemed to be in the low cash mode state, smart lock,providing a first notification to the customer when the account isdeemed to be in the low cash mode state, providing a second notificationto the customer when smart lock is activated, and presenting, with thesecond notification, at least one option to the customer to manage theaccount.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory only,and are not restrictive of the disclosed embodiments as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the associating a card with the first account description,serve to explain the disclosed embodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system environment, consistentwith disclosed embodiments;

FIGS. 2A-2D illustrate block diagrams of exemplary methods of linkingfinancial accounts, consistent with disclosed embodiments;

FIGS. 3A-3B illustrate exemplary bank account webpages for use withapplications, consistent with disclosed embodiments;

FIGS. 4A-4E illustrate exemplary graphical user interfaces (GUIs) formanaging a financial account in a low cash mode, consistent withdisclosed embodiments;

FIGS. 5A-5D illustrates exemplary graphical user interfaces for low cashmode customization and configurations, consistent with disclosedembodiments;

FIGS. 6A-6C illustrate exemplary graphical user interfaces fordisplaying available balance user alerts, consistent with disclosedembodiments;

FIGS. 7A-7C illustrate exemplary graphical user interfaces forpredicting a low cash mode and related expenses, consistent withdisclosed embodiments;

FIGS. 8A-8B illustrates exemplary graphical user interfaces having adashboard configuration for managing a financial account in low cashmode, consistent with disclosed embodiments;

FIGS. 9A-9E illustrates exemplary graphical user interfaces having adashboard configuration for payment control and review of transactions,consistent with disclosed embodiments;

FIGS. 10A-10C illustrate exemplary graphical user interfaces having afirst disabled dashboard embodiment, consistent with disclosedembodiments;

FIGS. 11A-11B illustrates exemplary graphical user interfaces having asecond disabled dashboard embodiment, consistent with disclosedembodiments;

FIG. 12 illustrates an exemplary graphical user interface for a bankapplication enabling payment control, consistent with disclosedembodiments;

FIGS. 13A-13D illustrates exemplary graphical user interfaces for a bankapplication enabling smart lock triggers, consistent with disclosedembodiments;

FIGS. 14A-14B illustrates exemplary graphical user interfaces for a bankapplication enabling a smart geolocation feature, consistent withdisclosed embodiments;

FIGS. 15A-15B illustrates exemplary graphical user interfaces forspending control and automatic locking, consistent with disclosedembodiments;

FIGS. 15C-15D illustrates exemplary graphical user interfaces for dangerday feature setting and geolocation control features, consistent withdisclosed embodiments;

FIG. 16 illustrates an exemplary flow chart for managing a financialaccount in low-cash mode, consistent with disclosed embodiments.

FIG. 17 illustrates an exemplary flow chart for providing notificationsto a customer, consistent with disclosed embodiments.

FIG. 18 illustrates an exemplary flow chart for managing a financialaccount, consistent with disclosed embodiments.

FIG. 19 illustrates an exemplary flow chart for managing a financialaccount, consistent with disclosed embodiments.

FIG. 20 illustrates an exemplary flow chart for multi-factorauthentication, consistent with disclosed embodiments.

FIG. 21 illustrates an exemplary flow chart for providing notificationto a customer, consistent with disclosed embodiments.

FIG. 22 illustrates an exemplary flow chart for providing notificationto a customer, consistent with disclosed embodiments.

FIG. 23 illustrates an exemplary flow chart for preventing a negativeaccount balance, consistent with disclosed embodiments.

FIG. 24 illustrates an exemplary flow chart for preventing a negativeaccount balance, consistent with disclosed embodiments.

FIG. 25 illustrates an exemplary flow chart for predicting low-cashmode, consistent with disclosed embodiments.

FIG. 26 illustrates an exemplary flow chart for managing a financialaccount, consistent with disclosed embodiments.

FIG. 27 illustrates an exemplary flow chart for managing a financialaccount, consistent with disclosed embodiments.

FIG. 28 illustrates an exemplary flow chart for managing a financialaccount, consistent with disclosed embodiments.

FIG. 29 illustrates an exemplary flow chart for generating apersonalized grace period, consistent with disclosed embodiments.

FIG. 30 illustrates an exemplary flow chart for managing a financialaccount, consistent with disclosed embodiments.

FIG. 31 illustrates an exemplary flow chart for predicting cash flow,consistent with disclosed embodiments.

FIG. 32 illustrates an exemplary flow chart for preventing a negativeaccount balance, consistent with disclosed embodiments.

FIG. 33 illustrates an exemplary flow chart for preventing a negativeaccount balance, consistent with disclosed embodiments.

FIG. 34 illustrates an exemplary flow chart for preventing a negativeaccount balance, consistent with disclosed embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar parts.While several illustrative embodiments are described herein,modifications, adaptations and other implementations are possible. Forexample, substitutions, additions, or modifications may be made to thecomponents illustrated in the drawings, and the illustrative methodsdescribed herein may be modified by substituting, reordering, removing,or adding steps to the disclosed methods. Accordingly, the followingdetailed description is not limited to the disclosed embodiments andexamples. Instead, the proper scope is defined by the appended claims.

As used herein, low-cash mode may be used to refer to a state of anaccount held by a customer at a financial service provider when thefinancial service provider determines that the account has insufficientfunds to handle a transaction without resulting in a negative balance,that the account has a negative balance, that the account balance may benegative as a result of scheduled or predicted future transactions, orthat the account balance has fallen below a predetermined thresholdvalue.

FIG. 1 is a diagram illustrating exemplary system environment 100 inaccordance with the disclosed embodiments. The components andarrangements shown in FIG. 1 are not intended to limit the disclosedembodiments, as the components used to implement the disclosed processesand features may vary. System environment 100 may include one or morenetworks 102, financial institutions 106, third-party service providers110, and user devices 108. Each of the networks 102, financialinstitutions 106, and third-party service providers 110 may comprise oneor more computing devices or servers, databases, cloud services, and/orinternal networks. Other components known to one of ordinary skill inthe art may be included in system environment 100 to gather, process,transmit, receive, acquire, and provide information used in conjunctionwith the disclosed embodiments. In addition, system environment 100 mayfurther include other components that perform or assist in theperformance of one or more processes that are consistent with thedisclosed embodiments.

In some embodiments, system environment 100 may include one or morenetworks 102. Network 102 may comprise any computer networkingarrangement used to exchange data. For example, network 102 may be theInternet, a private data network, a virtual private network (VPN) usinga public network, and/or other suitable connections that enable thecomponents of system environment 100 to send and acquire information.Network 102 may also include a public switched telephone network(“PSTN”) and/or a wireless network such as a cellular network, wiredWide Area Network, Wi-Fi network, and/or another known wireless network(e.g., WiMAX) capable of bidirectional data transmission.

Each network 102, financial institution 106, and third-party serviceprovider 110 may also include one or more local networks (not shown). Alocal network may be used to connect the components of FIG. 1 , such asfinancial institution 106, user device 108, and third-party serviceprovider 110 to network 102. A local network may comprise any type ofcomputer networking arrangement used to exchange data in a localizedarea, such as Ethernet, Wi-Fi based on IEEE 802.11 standards,Bluetooth™′ and other suitable network protocols that enable componentsof system environment 100 and other servers, computers, and systems ofcomponents of system environment 100 to interact with one another and toconnect to network 102. In some embodiments, a local network comprises aportion of network 102. In other embodiments, components of systemenvironment 100 may communicate via network 102 without a separate localnetwork.

In some embodiments, system environment 100 may include one or more userdevices 108. User device 108 may be one or more of a desktop computer, alaptop, a tablet, a smartphone, a multifunctional watch, a pair ofmultifunctional glasses, a tracking device, or any suitable device withcomputing capability. User device 108 may comprise a memory, aprocessor, and/or other specialized hardware that is configured toexecute one or more methods of the disclosed embodiments. User device108 may have an online banking or financial account managementapplication installed thereon, which may enable user device 108 tocommunicate with, for example, with financial institution 106 and/orthird-party service provider 110 via network 102 and/or a local network.Additionally, user device 108 may connect to financial institution 106and/or third-party service provider 110 through use of web browsersoftware via network 102 and/or a local network. Finally, user device108 may provide a graphical user interface 118 to enable users to viewdata from the user device 108 generated by an application thereon andobtained over network 102 from one or more of financial institution 106and/or third-party service provider 110.

In some embodiments, one or more of financial institution 106,third-party service provider 110, and/or network 102 may include one ormore databases. Database may include one or more memory devices thatstore information. By way of example, databases may include Oracle™databases, Sybase™ databases, or other relational databases ornon-relational databases, such as Hadoop sequence files, HBase™, orCassandra™. The databases or other files may include, for example, dataand information related to the source and destination of a networkrequest, the data contained in the request, etc. Systems and methods ofdisclosed embodiments, however, are not limited to separate databases.Database may include computing components (e.g., database managementsystem, database server, etc.) configured to acquire and processrequests for data stored in memory devices of database and to providedata from database.

In some embodiments, one or more of financial institution 106,third-party service provider 110, and/or network 102 may include one ormore cloud services. Cloud service may include a physical and/or virtualstorage system associated with cloud storage for storing data andproviding access to data via a public network such as the Internet.Cloud service may include cloud services such as those offered by, forexample, Amazon®, Apple®, Cisco®, Citrix®, IBM®, Joyent®, Google®,Microsoft®, Rackspace®, Salesforce.com®, and Verizon®/Terremark®, orother types of cloud services accessible via network 102. In someembodiments, cloud service comprises multiple computer systems spanningmultiple locations and having multiple databases or multiple geographiclocations associated with a single or multiple cloud storage service(s).As used herein, cloud service refers to physical and virtualinfrastructure associated with a single cloud storage service and maymanage and/or store data.

In some embodiments, one or more of financial institution 106,third-party service provider 110, and/or network 102 may include one ormore servers or clusters of servers. Servers or clusters of servers maybe located in the same data center or different physical locations.Multiple servers and clusters may be formed as a grid to share resourcesand workloads. Each server and/or cluster may include a plurality oflinked nodes operating collaboratively to run various applications,software modules, analytical modules, rule engines, etc. Each node maybe implemented using a variety of different equipment, such as asupercomputer, personal computer, a server, a mainframe, a mobiledevice, or the like. In some embodiments, the number of servers and/orserver cluster may be expanded or reduced based on workload. In someembodiments, one or more components of system environment 100 may beplaced behind a load balancer to support high availability and ensurereal-time (or near real-time) processing of optimal decisionpredictions.

In some embodiments, one or more of financial institution 106,third-party service provider 110, and/or network 102 may include one ormore computing systems that are configured to execute softwareinstructions stored on one or more memory devices to perform one or moreoperations consistent with disclosed embodiments. For example, afinancial institution 106 may include memory devices storing data andsoftware instructions and processors configured to use the data andexecute the software instructions to perform server-based functions andoperations known to those skilled in the art. Financial institution 106may also include one or more general-purpose computers, mainframecomputers, or any combination of these types of components. In someembodiments, financial institution 106 may have an application installedthereon to perform processes that are consistent with disclosedembodiments.

In some embodiments, one or more of financial institution 106,third-party service provider 110, and/or network 102 may include devicesconfigured as a particular apparatus, system, or the like based on thestorage, execution, and/or implementation of the software instructionsthat perform operations consistent with disclosed embodiments. Devicesof financial institution 106 may be standalone or may be part of asubsystem included in a larger system. For example, financialinstitution 106 may include distributed servers that are remotelylocated and communicate over a network (e.g., WAN and/or a localnetwork) or a dedicated network.

In some embodiments, one or more of financial institution 106,third-party service provider 110, and/or network 102 may include or mayaccess one or more storage devices configured to store data and/orsoftware instructions used by one or more processors to performoperations consistent with disclosed embodiments. For example, financialinstitution 106 may include memory configured to store one or moresoftware programs that perform several functions when executed by aprocessor. The disclosed embodiments are not limited to separateprograms or computers configured to perform dedicated tasks. Forexample, financial institution 106 may include memory that stores asingle program or multiple programs. Additionally, one or more offinancial institution 106, third-party service provider 110, and/ornetwork 102 may execute one or more programs located remotely. Forexample, financial institution 106 may access one or more remoteprograms stored in memory included with a remote component that, whenexecuted, perform operations consistent with disclosed embodiments. Forexample, financial institution 106 may exchange data and interact withsystems, devices, and programs of third-party service provider 110and/or hardware and software of user device 108. In certain aspects, oneor more of financial institution 106, third-party service provider 110,and/or network 102 may include server software that generates,maintains, and provides services associated with user accounts.

Financial institution 106 in system environment 100 may include anyentity that generates, provides, manages, and/or maintains financialservice accounts 130, etc., for customers. Financial institution 106 mayinclude a retail and commercial bank, internet bank, credit union,savings and loan association, investment bank or company, brokeragefirm, and/or another financial institution known by those of skill inthe art. Financial institution 106 may provide and maintain one or morefinancial service accounts 130 for an account owner. The one or moreaccounts 130 may include, among others types, a checking account, asavings account, certificate of deposit account, money market account,brokerage account, investment retirement account (IRA), 401(k) account,line of credit, and/or any other financial account known by those ofskill in the art. System environment 100 may include more than onefinancial institution 106 with one or more financial accounts 130, asingle financial institution 106 with two or more financial accounts130, or any other combination thereof. In the context of the disclosedembodiments, the present embodiments include multiple accounts,including at least a first account and second account, including thosesituated in one or more financial institutions, owned by one or moreaccount owners, and of one or more account type.

Each financial account 130 in system 100 may have differing oroverlapping account ownership and access privileges. For example, thefinancial accounts 130 may be individual accounts, joint accounts,payable-on-death accounts, joint account with rights of survivorship,accounts in trust, or any other type of account ownership known by thoseof skill in the art. For example, an individual account may include asingular account owner. A joint account may include two or more accountowners with equal access to funds and information related to theaccount. Accounts in trust may be controlled by a designated trustee forthe benefit of another account owner, who may have limited access orcontrol over the trust account. It is not desired to limit the type offinancial account 130 used in the present embodiments.

Third-party service provider 110 may be any company, organization, orentity that may enable, monitor, coordinate, and/or control access andprovide information to different account owners of different financialaccounts 130 in system environment 100. Third-party service provider 110may communicate with one or more financial institutions 110 and one ormore customers via one or more user devices 108 and enable access toaccount information and manage access rights to different financialaccounts 130. Third-party service provider 110 may serve as aninformation clearinghouse or intermediary between financial institution106 and user device 108. For example, account owners may grantthird-party service provider 110 access to certain information forfinancial accounts 130 maintained by one or more financial institution106. Financial institution 106 may securely publish data to third-partyservice provider 110 for particular financial accounts whose owners havegranted access, and particular data from those accounts, over a secureprotocol or public or private network, and third-party service provider110 may control access to the information between different accountowners. In one embodiment, account owner of financial account 130 maygrant access to information from the account, whereby financialinstitution 106 enables third-party service provider 110 to accessaccount data via an application programming interface (API) or othermeans, and share data with an owner of another financial account. Thetwo accounts are thereby linked by third-party service provider 110having access to certain data in each account and publishing that datato the different account owners. This enables, for instance, an owner ofa first account to see transactions in a second account. Certainpersonal and financial data may be obfuscated or not shared bythird-party service provider 110, or financial institution 106 may notprovide such information, upon request and based on the scope of accessenabled by an account owner. These data sharing functions may also becarried out, in certain embodiments, by one or more financialinstitution 106 directly with account owners and without third-partyservice provider 110.

As will be discussed in greater detail below, account owners mayestablish rules to transfer money from a first account to a secondaccount (or a third account) based on activity in the first account.Account owners may also establish rules to transfer money from a secondaccount to a first account (or a third account) based on activity in thesecond account. Rules may be established and stored in an accountowner's financial account 130 by financial institution 106, in a serviceaccount 140 of third-party service provider 110, or both. Rules may beestablished by account owners via graphical user interface 118 of userdevice 108 for, among other things, determining when to transfer funds,determining how much to transfer, and determining what restrictions areplaced on transferred funds, transfer amounts, and transfer rates.

One or more financial institutions 106 and/or one or more third-partyservice providers 110 may host a web application, API, web site, orsimilar interface that is accessible over network 102 to account ownersvia user device 108. The interface may be hosted on one or more webservers and operate in a client-server model with user device 108, whileobtaining information, including account information, from serviceprovider 110 and/or financial institution 106. Via user device 108, anaccount owner may view graphical user interface 118 on user device 108.Graphical user interface 118 may provide account owners with the abilityto view financial account information of another account, for example,another account owner's account. Graphical user interface 118 may alsoprovide an interface enabling the disclosed functions herein, including,among other things, authorizations to transfer cash and/or funds(assets), authorizations to share information and connect and/or linkfinancial accounts, establish rules for transferring cash and/or funds(assets) between linked accounts, and track and monitor transfers andthe status of financial accounts.

System for Low-Cash Mode

As disclosed herein, low-cash mode may be used to refer to a state of anaccount held by a customer at a financial service provider when thefinancial service provider determines that the account has insufficientfunds to handle a transaction without resulting in a negative balance,that the account has a negative balance, that the account balance may benegative as a result of scheduled or predicted future transactions, orthat the account balance has fallen below a predetermined thresholdvalue.

Consistent with the present embodiments, financial institution 106, 116may provide the customer at user device 118 with options to manageaccounts 131, 132 in low cash mode including methods, systems, andfeatures disclosed herein which provide the customer the ability to atleast increase the balance of accounts 131, 132 (e.g. personal loan,transfer of cash and/or funds), approve or deny individual transactions,lock a card associated with accounts 131, 132, or prevent spending inorder to avoid a negative account balance. Additionally, methods,systems, and features disclosed herein may provide the customer theability to prioritize payments, cancel transactions, manage the amountof a negative balance or length of time carrying a negative balance inorder to minimize negative balance fees, select repayment options whenan overdraft cannot be avoided, and other options and features which thecustomer can select in order to avoid or minimize a negative accountbalance.

System for Alerting to Customers when Entering/Exiting Low-Cash Mode

Consistent with disclosed embodiments, a financial institution mayprovide a notification to a customer when an account associated with thecustomer enters low cash mode in the form of an alert. The notificationmay be triggered when an account balance is negative; when an accountbalance falls below a predetermined threshold; during a particular timeof the month that is determined based on scheduled reoccurringtransactions such as direct deposits and automatic billing as well asanalysis of historical data; determined based on transaction daterelated to upcoming holidays, birthdays, anniversaries, or calendaredspecial occasions; triggered when a customer is interacting with amerchant online; or determined based on geographic location of acustomer or merchant. The notification may be delivered to the customeras an email, text message, voice call, alert through an application on amobile phone, social media alert, alert through a mobile device, alertthrough wearable technology, alert through a device connected to theinternet, or other methods for instantaneously alerting a customer.

The notification may further include information relating to anynegative balance fees to be assessed if the negative balance is notcured and a period of time to cure negative balance. In someembodiments, the negative balance fees may be tiered based on, forexample, the extent to which the account is negative or the length oftime the account balance is negative.

FIG. 4B illustrates an exemplary graphical user interface 414 forproviding an intelligent low balance alert 418 to a customer, consistentwith disclosed embodiments.

Consistent with disclosed embodiments, financial institution may alsoprovide a notification to a customer when the account associated withthe customer is no longer in low cash mode. The notification may betriggered when a customer cures a negative balance; when the accountbalance is greater than a predetermined threshold balance; a particulartime of the month is past; a time period related to upcoming holidays,birthdays, anniversaries, or calendared special occasions has past; orthe financial institution determines the customer is no longer in dangerof incurring a negative balance based on a change in geographic locationof a customer. The notification may be delivered to the customer as anemail, text message, voice call, alert through a mobile bankingapplication, social media alert, alert through a mobile device or mobiledevice application, alert through wearable technology, alert through adevice connected to the internet, or other means for instantaneouslyproviding an alert to the customer.

As shown in FIG. 4B, a notification on a mobile device may link to anapplication on a mobile device. The application on the mobile device maydisplay a textual alert 416. The textual alert may provide informationincluding that an account has entered low cash mode, the accountbalance, time remaining to cure the negative balance, options for curingthe negative balance, and/or options for minimizing negative balancefees. For example, textual alert 416 may indicate “Low Cash Mode isactive. You have a negative available balance of −$120.00. Reviewoptions.” Textual alert 416 may prompt a customer operating user device108 to review options for replenishing the account so as to achieve apositive balance and/or remove the account from low cash mode. Nextbutton 420 and skip button 422 may enable a user to take a next step inthe process of reviewing options and/or skip the process of reviewingoptions entirely.

FIGS. 6A-6C illustrate exemplary graphical user interfaces fordisplaying available balance user alerts, consistent with disclosedembodiments. FIG. 6A illustrates an exemplary graphical user interfacefor displaying an alert of a negative available balance, consistent withdisclosed embodiments. As shown in FIG. 6A, graphical user interface 602may include an intelligent alert message 604 that indicates “Low CashMode is active. You have a negative available balance of $−200.00.Review options.” FIG. 6B illustrates an exemplary graphical userinterface for displaying an alert of a balance outside of low cash mode,consistent with disclosed embodiments. As shown in FIG. 6B, graphicaluser interface 606 may include an intelligent alert message 608 thatindicates “You have an available balance of $60.86. You are out of LowCash Mode.” FIG. 6C illustrates an exemplary graphical user interfacefor displaying an alert of a non-payments, consistent with disclosedembodiments. As shown in FIG. 6C, graphical user interface 610 mayinclude an intelligent alert message 612 that indicates “Low cash modeis active. Your available balance is $80.31, and 1 payment won't bepaid. Review options.” Other intelligent alerts may be contemplated.

FIG. 17 illustrates an exemplary flow chart for providing notificationsto a customer. At step 1702, financial institution 106 may associate acustomer with an account at the financial institution. At step 1704,financial institution 106 may associate the account with a mobile device108. At step 1706, financial institution 106 may determine an accountbalance of the account.

At step 1708, financial institution 106 may determine, based on theaccount balance, whether the account is deemed to be in a low-cash modestate, as disclosed herein. At step 1710, if the account is deemed to bein a low-cash mode state, financial institution 106 may provide anotification to the customer that the account is deemed to be in alow-cash mode state. At step 1712, financial institution 106 may presentoptions to manage the account while the account is in the low-cash modestate.

System for Preventing Overdraft

Consistent with disclosed embodiments, the financial institution mayoffer customers various options to avoid negative account balances andassociated negative balance fees. The financial institution may offerthe customers options disclosed herein including, for example, theability to transfer money between accounts, the ability to cancelpending transactions or payments, the ability to obtain a loan, or theability to accelerate ACH transactions or payroll deposits. Theseoptions may be offered to the customers by the financial institutionthrough various methods, including through an application on a mobiledevice. In some embodiments, these options may be selectable by thecustomer and implemented automatically, without any action orintervention by the financial institution.

Consistent with disclosed embodiments, the financial institution maypresent the option to the customer of obtaining or applying for apersonal loan in order to avoid a negative account balance. Financialinstitution may present this option to the customer with a preapprovedamount and an interest rate for immediate approval and deposit of theamount into the account. Additionally or alternatively, the customer maychoose to customize the terms of the loan, subject to approval by thefinancial institution.

In FIG. 2B, first account 131 and second account 132 may be maintainedwithin separate financial institutions 106, 116. As noted above, firstaccount 131 and second account 132 may have differing, overlapping, oridentical account ownership. As with FIG. 2A, third-party serviceprovider 110 may be a third-party entity acting as an informationclearing house or intermediary between financial institutions 106, 116,and one or more user devices 108. Consistent with this presentembodiment, either financial institution 106 or financial institution116 may present options to customers with at least one account in lowcash mode or when an account balance in first account 131 (or secondaccount 132) drops beneath a predetermined threshold value. Financialinstitution 106 may present the option of obtaining/applying for apersonal loan in order to avoid an overdraft of first account 131 (orsecond account 132). Either financial institution 106 or financialinstitution 116 may present this option to the customer with apreapproved amount and an interest rate for immediate approval anddeposit of the amount into first account 131 (or second account 132).Additionally or alternatively, the customer may choose to customize theterms of the loan, subject to approval by the financial institution.

In FIG. 2C, first account 131 and second account 132 may be maintainedwithin a common financial institution 106 and involve differing,overlapping, or identical account ownership. In this present embodiment,financial institution 106 may communicate directly with account ownersvia user device 108, without third-party service provider 110. Aplurality of user devices 108 (not shown) associated with the accountowner or owners may receive communication from financial institution106. Consistent with this present embodiment, financial institution 106may present options to customers with at least one account in low cashmode or when an account balance in first account 131 (or second account132) drops beneath a predetermined threshold value. Financialinstitution 106 may present the option of obtaining/applying for apersonal loan in order to avoid an overdraft of first account 131 (orsecond account 132). Financial institution 106 may present this optionto the customer with a preapproved amount and an interest rate forimmediate approval and deposit of the amount into first account 131 (orsecond account 132). Additionally or alternatively, the customer maychoose to customize the terms of the loan, subject to approval by thefinancial institution.

In FIG. 2D, first account 131 and second account 132 may be maintainedwithin different financial institutions 106, 116, involve differing,overlapping, or identical account ownership, and financial institutions106, 116 may communicate directly with account owners via user device108 without third-party service provider 110. A plurality of userdevices 108 (not shown) associated with the account owner or owners mayreceive communication from financial institutions 106, 116. Consistentwith this present embodiment, either financial institution 106 orfinancial institution 116 may present options to customers with at leastone account in low cash mode or when an account balance in first account131 (or second account 132) drops beneath a predetermined thresholdvalue. Financial institution 106 may present the option ofobtaining/applying for a personal loan in order to avoid an overdraft offirst account 131 (or second account 132). Either financial institution106 or financial institution 116 may present this option to the customerwith a preapproved amount and an interest rate for immediate approvaland deposit of the amount into first account 131 (or second account132). Additionally or alternatively, the customer may choose tocustomize the terms of the loan, subject to approval by the financialinstitution.

Additionally or alternatively, the preventative options may furtherinclude the ability to accelerate pending ACH deposits or a regularlyscheduled deposit including, for example, a payroll deposit. Thefinancial institution may accelerate the deposits by expeditingprocessing, providing the funds as a loan from the financial institutionfor little or no cost as a loan for the amount of the future deposit,waiting to process withdrawals until the deposit has been processed, orother means known in the art used to accelerate deposits.

FIG. 18 illustrates an exemplary flow chart for providing notificationsto a customer. At step 1802, financial institution 106 may associate acustomer with a first account at financial institution 106. At step1804, financial institution 106 may associate the customer with a secondaccount at financial institution 106 or a different financialinstitution. At step 1806, financial institution 106 may link the firstaccount with the second account. At step 1808, financial institution 106may determine an account balance of the first account.

At step 1810, financial institution 106 may determine, based on thefirst account balance, whether the account is deemed to be in a low-cashmode state, as disclosed herein. At step 1812, if the account is deemedto be in a low-cash mode state, financial institution 106 mayautomatically transfer funds from the second account to the firstaccount. The amount of funds transferred may be preselected by thecustomer or determined by financial institution 106. Additionally oralternatively, the amount of funds transferred may be sufficient suchthat the first account is no longer deemed to be in the low-cash modestate or sufficient to prevent a negative first account balance.

At step 1814, financial institution 106 may provide a notification tothe customer that the first account is deemed to be in a low-cash modestate, that funds were automatically transferred from the secondaccount, the amount of funds transferred from the second account, acurrent first account balance, and/or options for managing the firstaccount while in the low-cash mode state.

System for Tiered Overdraft Fees

In other embodiments, a financial institution may charge a negativebalance fee when a transaction results in a negative account balance. Insome embodiments, the financial institution may assess the negativebalance fees using a tier system. The tiered negative balance fees maybe based on, for example, the extent to which the account is negativewith higher fees for larger negative amounts as compared to smallernegative amounts or based on historical data associated with theaccount.

System for Synthetic Data and Machine learning

Consistent with disclosed embodiments, the financial institution mayinclude data privacy and security measures in order to protecttransaction, account, and customer data. Financial institution may use,for example, encryption/decryption, tokenization/detokenization,masking, obfuscation, or other methods for protecting data. Additionallyor alternatively, financial institution may employ artificialintelligence or machine learning algorithms to protect transaction,account, and customer data. The artificial intelligence or machinelearning algorithms may also be used to generate synthetic data orartificial data stored in a data platform to be substituted fortransmitted data or for fields in transmitted data that are deemedsensitive by the costumer or financial institution.

System for Fraud Protection Features

Consistent with disclosed embodiments, financial institution mayintegrate fraud protection features with the features associated with anaccount in low-cash mode. Fraud protection features may include securityquestions, multi-factor authentication, password standards, alertsassociated with suspicious activity, and any other feature or serviceintended to prevent, detect, or resolve fraud. Password standards mayinclude minimum password requirements such as length or characterrequirements.

Security questions may include a set of questions and answers whereinthe customer or account holder provides answers to questions whencreating an account. The customer-provide answers to the questions arestored by the financial institution and used to verify the identity ofthe customer. The questions and answers are setup such that only thecustomer should be able to provide the specific answer to the specificquestions. The financial institution may prompt a customer for theanswers to security questions when the customer attempts to login to theaccount from a computer or mobile device not previously associated withthe account.

In one example, multi-factor authentication may include, when a customerlogs into an account, generating a one-time passcode such as a randomstring of characters and sending the one-time passcode to a device(e.g., as a text message, email, or voice call), prompting the customerfor entry of one-time passcode, validating the entered passcode, andpermitting access to the account.

FIG. 20 illustrates an exemplary flow chart for multi-factorauthentication. At step 2002, financial institution 106 may receive alogin attempt to access an account with financial institution 106. Atstep 2004, financial institution 106 may generate a one-time passcode tobe used to verify the identity of the customer. At step 2006, financialinstitution 106 may send the one-time passcode to the customer, forexample in a text message, email, or voice call.

At step 2008, financial institution 106 may prompt for entry of theone-time passcode. At step 2010, financial institution 106 may receiveentry of the passcode. At step 2012, financial institution 106 mayvalidate the passcode received in order to ensure that the passcodereceived matches the one-time passcode that was generated and sent. Atstep 2014, if the received passcode is validated, then financialinstitution 106 may grant the customer access to the account.

System for Integration with PNC Virtual Wallet

Consistent with disclosed embodiments, the financial institution mayprovide options allowing customers to perform actions relating to lowcash mode through a website, a mobile version of a website, anapplication or a micro-application on a mobile device, or through anancillary application, such as a budgeting or money-managementapplication, for example PNC Mobile Wallet®.

FIGS. 8A-8B illustrates exemplary graphical user interfaces having adashboard configuration for managing a financial account in low cashmode, consistent with disclosed embodiments. As shown in FIGS. 8A-8B,there are subsections for virtual wallet spread at 804, such assubsections 806, 808, 810, 814, 816, 820, 822, 824. The user may bepresented with a notification indicating that “You're in Low Cash Mode.Your default mode is to pay checks and automatic payments” at 806. At808, an indication may provide “Smart Lock is enabled. Your debit cardis locked.” Payment control 810 is another subsection. For paymentcontrol 810, the user can choose to override the default setting. Theuser can also select payments available for review 812. At 814, the usercan select extra time, which is the time remaining to bring the accountbalance to at least $0.00 before the user is charged a daily overdraftfee. At 816, dashboard provides funding options where a user can fundthe account. At 818, the user may select an option to make a transfer.At 820, the user may make a deposit. At 822, the user may be able tofind an ATM. At 824, the user may return to an account home page. FIG.8B displays a user interface out of low cash mode 830. When out of lowcash mode, the user's account may process automatic payments and checkswill be paid. For example, at 832, the Verizon Wireless bill will bepaid. At 834, Columbia gas utility bill will be paid. At 835, a checkwill be paid.

System for Linking with Virtual Wallet and Social Media

In some embodiments, the financial institution may urge or permitcustomers to link financial accounts with social media accounts. Thelink between accounts may provide financial institution with access toinformation gathered by the social media account and associatedapplications. The link may also provide another channel for financialinstitution to send alerts or messages to a customer. For example, acustomer could receive a message via a social network instant or directmessage that the account has entered low cash mode.

Additionally or alternatively, the financial institution may provide acustomer with the option to associate a social media account associatedwith the customer with a financial account. The financial institutionmay then interact with the customer using the notifications andinfrastructure provided by the social media platform. For example, thefinancial institution may provide a notification that an accountassociated with a user has entered low cash mode using FacebookMessenger or Twitter Direct Message. The financial institution may alsoaccess or analyze data associated with a customer's social mediaprofile, presence, usage, activity, connections, or other social mediadata.

System for Pre-Purchase Alerts

Consistent with disclosed embodiments, the financial institution mayprovide a notification to a customer that a pending, scheduled, oranticipated purchase or transaction will result in a negative accountbalance before the purchase or transaction is made. For example, afinancial institution may notify a customer that a transactionassociated with an item placed in a virtual shopping cart while visitingan online merchant would result in a negative balance. In anotherembodiment the financial institution may use historical data associatedwith a customer to predict and notify a customer that an anticipatedtransaction will result in a negative balance. The financial institutionmay further anticipate transactions based on the time of the day, month,or year; a geographic location associated with a merchant; a geographiclocation associated with the customer; or other indicators associatedwith the customer and spending an amount greater than a current balance.

FIG. 23 illustrates an exemplary flow chart for preventing a negativeaccount balance. At step 2302, financial institution 106 may associate acustomer with an account at the financial institution. At step 2304,financial institution 106 may associate the account with a device 108.At step 2306, financial institution 106 may determine an account balanceof the account.

At step 2308, financial institution 106 may determine, based on theaccount balance, whether the account is deemed to be in a low-cash modestate, as disclosed herein. At step 2310, financial institution mayidentify a potential purchase and the amount of the potential purchase.At step 2312, financial institution 106 may, based on the accountbalance and potential purchase amount, determine a potential accountbalance. At step 2314, financial institution 106 may provide anotification to the customer. The notification may include a predicatedaccount balance, options to prevent a negative balance, options to avoidthe account entering the low-cash mode state, or additional informationand options for managing the account as disclosed herein.

System for Overall Increased Efficiency of Transactions

Implementation of the disclosed embodiments may result in overallincreased efficiency of transactions by financial institution 106. Theincreased efficiency may result from at least improved capability totransfer funds between accounts, automation of high demand or regularlyoccurring tasks/queries such as balance confirmation, by storing anddisplaying more information in the same place, by providing quickersearching of transaction data, providing additional avenues forcommunicating with customers, providing more effective avenues forcommunicating with customers, and other features discussed below whichimprove functionality for the customers or financial institution 106.Additionally or alternatively, the disclosed embodiments may increasecustomer satisfaction with the financial institution and improvecustomer loyalty.

System for Automatic Card Lock

Consistent with disclosed embodiments, when an account associated with acustomer enters low cash mode, the financial institution may disable,reject, or block transactions initiated by a credit or debit cardassociated with the account. The notification (disclosed above) mayinform the customer that an account has entered low cash mode and thatany card associated with the account has been locked. The financialinstitution may provide the customer with the ability to choose theoption to have the financial institution of automatically locking anycard when the associated account enters low cash mode. The financialinstitution may also provide the customer with the ability to unlock acard that has been locked due to the account's entry into low cash mode.These options and functionality may be provided by the financialinstitution through a mobile application or web-based interface.

FIG. 24 illustrates an exemplary flow chart for preventing a negativeaccount balance. At step 2402, financial institution 106 may associate acustomer with an account at the financial institution. At step 2404,financial institution 106 may associate the account with a card such asa debit card or credit card. At step 2406, financial institution 106 maydetermine an account balance of the account.

At step 2408, financial institution 106 may determine, based on theaccount balance, whether the account is deemed to be in a low-cash modestate, as disclosed herein. At step 2410, financial institution mayreceive a transaction initiated by the card associated with the account.At step 2412, if the account is deemed to be in a low-cash mode state,financial institution 106 may automatically deny the transactioninitiated by the card.

System for Low-Cash Mode Based on Predicted Balance

Consistent with disclosed embodiments, the financial institution maydetermine that an account is in low cash mode based on a predictedbalance. The predicted balance may be determined by comparing historicaltransaction data with current transaction data and predicting a futurebalance by manipulating the current balance based on expectedtransactions, deposits, and withdrawals. In some embodiments, thefinancial institution may apply artificial intelligence or machinelearning algorithms to historical data associated with a customer oraccount in order to learn and predict transactions and spendingtendencies and thereby generate a predicted balance.

FIG. 7A illustrates an exemplary graphical user interface for notifyinga customer that an account associated with the customer may enter lowcash mode in a future time period, consistent with disclosedembodiments. As shown in FIG. 7A, a graphical user interface 702 mayprovide an intelligent alert 706 that indicates “Low Cash Mode ahead”and “We predict your account x2958 could enter low cash mode in the next3 days. Review your options.”

FIG. 19 illustrates an exemplary flow chart for providing notificationsto a customer. At step 1902, financial institution 106 may associate acustomer with a first account at financial institution 106. At step1904, financial institution 106 may associate the customer with a secondaccount at financial institution 106 or a different financialinstitution. At step 1906, financial institution 106 may link the firstaccount with the second account. At step 1908, financial institution 106may determine an account balance of the first account.

At step 1910, financial institution 106 may determine, based on apredicted first account balance, whether the first account will enter alow-cash mode state, as disclosed herein. At step 1912, if the accountis predicted to enter the low-cash mode state, financial institution 106may automatically transfer funds from the second account to the firstaccount. The amount of funds transferred may be preselected by thecustomer or determined by financial institution 106. Additionally oralternatively, the amount of funds transferred may be sufficient suchthat the first account is no longer predicted to enter the low-cash modestate or sufficient to prevent a negative first account balance.

At step 1914, financial institution 106 may provide a notification tothe customer that the first account is predicted to enter the low-cashmode state, that funds were automatically transferred from the secondaccount, the amount of funds transferred from the second account, acurrent first account balance, and/or options for managing the firstaccount while in the low-cash mode state.

FIG. 25 illustrates an exemplary process for prediction low-cash mode.At step 2502, financial institution 106 may associate a customer with anaccount at financial institution 106. At step 2504, financialinstitution 106 may store financial history data associated with thecustomer and/or the account. At step 2506, financial institution 106 mayaccess non-financial data. At step 2508, financial institution 106 mayanalyze the financial history data and the non-financial data. At step2510, financial institution 106 may determine a future account balanceof the account based on the analysis performed in step 2508. At step2512, financial institution 106 may determine, based on the futureaccount balance, whether the first account will enter a low-cash modestate, as disclosed herein.

System for Selecting Overdraft Protection Features

In the disclosed embodiments regarding payment designation options, thefinancial institution may offer such options through various methods,including through an application on a mobile device. In someembodiments, these options may be selectable by the customer andimplemented automatically without any action or intervention by thefinancial institution (e.g., without approval of the selected featuresby the financial institution).

FIG. 26 illustrates an exemplary process for managing a financialaccount. At step 2602, financial institution 106 may provide aninterface for managing a financial account. At step 2604, financialinstitution 106 may associate a customer with an account at financialinstitution 106. At step 2606, financial institution 106 may determinean account balance of the account.

At step 2608, financial institution 106 may determine, based on theaccount balance, whether the account is deemed to be in a low-cash modestate, as disclosed herein. At step 2610, if the account is deemed to bein a low-cash mode state, financial institution 106 may provide anotification to the customer that the account is deemed to be in alow-cash mode state. At step 2612, financial institution 106 may presentoptions to manage the account while the account is in the low-cash modestate.

System for Customer Management of Transactions

In some embodiments, financial institution may provide options to thecustomer with an account in low cash mode to select which transactionsto approve while other transactions are canceled or delayed. The optionspresented by the financial institution may also allow the customer toselect an order of the transactions for processing, resulting in aprioritization of processing transactions. The customer may furtherselect payments to delay until the occurrence of an event, such as adeposit, or for a specified length of time. The financial institutioncan vary the options presented based on the origin of an individualtransaction, for example presenting the option to cancel sometransactions while others can only be delayed. Different transactionorigins may include point of sale transactions, ACH transactions,checks, scheduled payments, or any other method of initiating a transferof funds into or out of an account.

In some embodiments the financial institution may offer a customer theoption to designate payments for processing or non-processing after apayment transaction has occurred. A financial institution may, forexample, receive data indicating that a payment transaction between amerchant and a customer account has occurred while the customer accountis in low cash mode, and may offer the customer the option ofdesignating that payment transaction for processing. In someembodiments, financial institution may additionally offer the customerthe option to designate future payments from that merchant or locationas payments which should be processed while the customer account is inlow cash mode.

In other embodiments, financial institution may offer customers theoption to designate payments to be delayed or canceled while theassociated account in operating in low cash mode. In some embodiments,payments may not be available to be designated for processing during lowcash mode unless criteria set by the financial institution or thecustomer are met. For example, the financial institution may not allowany payments to be designated for processing if the customer account isin delinquency, has a balance above or below a threshold, has anoverdraft or penalty fee outstanding, or has a customer account historyconsistent with other groups of customer accounts. As anotherillustrative example, the customer account may be associated withparental controls or a controlling agent. The financial institution maywithhold offering the customer designation options or may offer thecustomer the designation options but prevent the customer from makingdesignations unless the financial institution has received anauthorization from the customer's parent or controlling agent.

FIG. 4D illustrates an exemplary graphical user interface 430 for payingor rejecting individual checks and automatic payments, consistent withdisclosed embodiments. Consistent with disclosed embodiments, thefinancial institution may present the customer with preventativeoptions. Preventative options may include, for example, the ability tocancel transactions including Automated Clearing House (“ACH”)transactions and pending, uncashed checks. The financial institution mayprovide suggestions or recommendations of which transactions to canceland provide means for canceling the pending transactions. As shown inFIG. 4D, a user may also be given the option 432 to manually cancelpayment of a cell phone bill of $75.00 or may be given the option to paythe cell phone bill of $75.00. A user may toggle between “reject” or“pay” and cancel automatic bill transactions.

FIG. 5B illustrates an exemplary graphical user interface for setting adefault payment behavior 514, consistent with disclosed embodiments. Asshown in FIG. 5B, a user may choose their default payment behavior whentheir account is below their low cash threshold. The user will have theoption to pay or reject individual checks and automatic payments. Aswitch 516 may enable the user to toggle between default “Reject” and“Pay” options. As shown in FIG. 5B, switch 516 for the user's defaultpayment behavior is set to “Pay” individual checks and automaticpayments when the account is in low cash mode. That is, the user'sdefault behavior is to still pay checks and automatic payments even ifthe account balance is negative. Switch 516 may be set to a defaultbehavior “Reject,” which would automatically prevent checks andautomatic payments from processing, unless the user affirmativelydetermines to pay the check or automatic payment (or allow it toprocess). Back 508 and Continue 510 buttons may be provided for users tonavigate between screens to allow for further configuration orcustomization of low cash mode preferences or properties.

FIGS. 9A-9E illustrates exemplary graphical user interfaces including adashboard configuration for payment control and review of transactions,consistent with disclosed embodiments. At FIG. 9A, user interface 902may include a projected balance that may be displayed at 906 as part ofthe options for managing an accounts, such as payment control 904. Inthis example, without user input, the financial institution will processpending transactions as shown at 908, where, if no decision is made fora transaction, then the financial institution will attempt to pay it. At910, the user is provided an option to reject or pay the Verizonwireless bill. At 912, the user is provided an option to reject or paythe Columbia gas utility bill. At 914, the user is provided an option toreject or pay the check. At 916, the user has selected to reject paymentfor the cable company. The dashboard configuration may include an amountof time remaining for a user to choose to pay or reject a transaction.In this example, at 916 the user has 36 hours and 10 minutes to make thedecision. At 918, the user may obtain more information as to why allpayments are not visible here. At 920, the user may review and confirmthe decisions. At FIG. 9B, user interface 922 may show a startingbalance 926 and then a calculated ending balance after transactions arereturned. It may also include a reminder at 926 to reschedule thesepayments 928. Interface 922 may include back 930 and confirm 932buttons. FIGS. 9C-9E illustrate various embodiments of user interfaces934, 938, and 948. At FIGS. 9C-9E, starting balance 926 may bepresented. Extra time may be enabled at 936. Payments at 942 that appearhere include recent checks automatic payments. To view all otherpayments, go to view transactions. At 944, view transactions. At 946,the user may close interface 938. At 924 pending transactions may beshown. 952 may display Verizon wireless as an example and at 954 mayreturn to payment controls.

System for Account Management Over a Time Period

Consistent with disclosed embodiments, financial institution may providea customer with the option to approve or deny processing or initiationof transactions for a period of time, such as an entire day (asdiscussed above). Alternatively, the financial institution may providethe customer the ability to review options associated with individualtransactions. In one embodiment, the financial institution may provide anotification to the customer (as disclosed herein) that presents theoption to the customer to approve or deny spending for the day.

In another embodiment, financial institution may provide a notificationto the customer (as disclosed herein) that prompts the customer toconfigure how an account can spend for a specified period of time, suchas a day. The notification may direct the customer to open anapplication on a mobile device where the financial institution presentsoptions for processing transactions associated with an account withinthe specified period of time.

FIG. 27 illustrates an exemplary flow chart for managing a financialaccount. At step 2702, financial institution 106 may associate acustomer with an account at financial institution 106. At step 2704,financial institution 106 may determine an account balance of theaccount.

At step 2706, financial institution 106 may determine, based on theaccount balance, whether the account is deemed to be in a low-cash modestate, as disclosed herein. At step 2708, financial institution 106 maydetermine whether smart lock is activated or designated to be activatedwhen the account is deemed to be in the low-cash mode state. At step2710, financial institution 106 may provide a notification to thecustomer. The notification provided in step 2710 may include multiplenotifications. Additionally or alternatively, the notification mayinclude information relative to the low-cash mode state and/or optionsto manage the account.

System for Smart Lock

Consistent with disclosed embodiments, the financial institution mayprovide an option for a customer to lock a card associated with anaccount. When a card is locked, the financial institution will cancel ordecline transactions associated with the card. The lock may be initiatedautomatically when the balance of the account falls below apredetermined threshold. Additionally or alternatively, the financialinstitution may present the customer with the option to lock a cardthrough an interface such as an application on a mobile device. Thepredetermined threshold for locking the card may or may not be differentfor the threshold triggering low cash mode for the same account. Thefinancial institution may select a default predetermined value forlocking the card or, alternatively, present the customer with theability to set the predetermined threshold for locking the card. Thefinancial institution may present the customer with the option to unlocka card associated with a card through an interface such as anapplication on a mobile device. As shown in FIG. 4E, a smart lockfeature is enabled and a debit card is locked. In this example, whilethe debit card is locked, the user has chosen to allow all checks andautomatic payments to proceed in low cash mode.

FIG. 4E illustrates an exemplary graphical user interface 436 forviewing a virtual wallet spread and automatically locking a customer'sdebit card, consistent with disclosed embodiments.

FIG. 5C illustrates an exemplary graphical user interface 518 for debitcard smart lock, consistent with disclosed embodiments. As shown in FIG.5C, a user may automatically lock a debit card associated with theaccount to avoid spending when the account balance is low. For example,the user may “disable,” select $5, $10, $25, or $50 as threshold valuesto automatically lock the debit card. Debit card transactions will bedeclined when a user's account is below the predetermined amount (e.g.as shown in FIG. 5C, $5.00). FIG. 5C also includes a lock icon 524 whichis a smart lock icon that demonstrates to the user where to lock andunlock the debit card at any time. Back 508 and Continue 510 buttons maybe provided for users to navigate between screens to allow for furtherconfiguration or customization of low cash mode preferences orproperties.

FIGS. 11A-11B illustrate exemplary graphical user interfaces having asecond disabled dashboard embodiment, consistent with disclosedembodiments. At FIG. 11A, user interface 1102 may be disabled such thata user may only lock or unlock a car associated with the account. Forexample, smart lock is enabled at 1104. At 1104, a user's debit card maybe unlocked. In FIG. 11B, user interface 1106 illustrates that smartlock may still be enabled at 1108 but the user's debit card may now belocked. Other interfaces not shown, which illustrate a user togglebetween an unlocked and a locked state for use of debit card arecontemplated with disclosed embodiments.

FIGS. 13A-13D illustrates exemplary graphical user interfaces for amobile application enabling smart lock triggers, consistent withdisclosed embodiments. At user interface 1302, the user may enable smartlock at 1304. At 1306, there may be alert preferences provided to auser. At 1308, alerts may be made automatically during predicted dangerdays. At 1312, anytime my balance goes below a predetermined threshold,such as $50 dollars, an alert will be made to the user. At 1314, anytimemy account has a negative available balance an alert will be made to auser. At 1316, default payment behavior may be set for a user. At 1318,an option for how transactions should be handled when the account issmart locked and the user fails to respond to the alert may be set by auser. At 1320, the user may select the option to pay all transactionseven if it results in a negative balance (which is shown as checked by auser). At 1322, the user may select the option to decline alltransactions (unchecked).

At FIG. 13B, user interface 1324, a smart lock is turned on, to enableaccount spending, and states to please login to the application at 1326by selecting lock icon at 3928. FIG. 13C, illustrates a user interface1330 displaying an “Accounts To Do” screen including a PNC Smart Lock at1332 displaying a message at 1334 that “Your account is currently lockedby Smart lock. Swipe to unlock your account and allow spending today.”At 1340 there is a lock icon, and at 1336 there is an unlock icon. At1338 there is a swipe to unlock feature. At 1302, there is a bank smartlock interface. At FIG. 13D, there is another bank lock interface 1342for enabling smart lock 1344. In particular, there is an enable smartlock icon that can be selected allowing a user to select smart lockpreferences 1346. At 1348, an option for automatically during predicateddanger days go ahead. At 1350, an option for anytime my balance goesbelow $10 dollars. At 1352, an option for anytime my account has anegative balance. At 1354 there are smart lock alert preferences. At1356, an option for each morning to approve/deny all spending for theday. At 1358, “Alert me when I'm at frequently shopped locations thatI've chosen” is presented as an option that the user may select.

FIG. 28 illustrates an exemplary flow chart for managing a financialaccount. At step 2802, financial institution 106 may associate acustomer with an account at financial institution 106. At step 2804,financial institution 106 may determine an account balance of theaccount.

At step 2806, financial institution 106 may determine, based on theaccount balance, whether the account is deemed to be in a low-cash modestate, as disclosed herein. At step 2808, financial institution 106 maydetermine whether smart lock is activated or designated to be activatedwhen the account is deemed to be in the low-cash mode state. At step2810, financial institution 106 may receive a request or initiation of acard transaction. At step 2812, if smart lock is activated, financialinstitution 106 may deny the card transaction. At step 2814, financialinstitution may provide a notification to the customer, as disclosedherein.

System for Overdraft Protection—Additional Accounts

Consistent with present embodiments, a financial institution may presenta customer with the option to transfer funds from a different accountinto an account in low cash mode or into an account to prevent theaccount from entering low cash mode. Upon entry of an account into lowcash mode or in order to prevent an account from entering low cash mode,the financial institution may automatically transfer funds from apredetermined account into an account in low cash mode. Thepredetermined account may be a different account owned by the samecustomer in the same financial institution, owned by a differentcustomer in the same financial institution, owned by the same customerin a different financial institution, owned by a different customer in adifferent financial institution, or any other financial institutionaccount previously linked with the customer's account currently in lowcash mode (as discussed below). The predetermined account may also be acredit card or similar line of credit wherein the balance of thetransaction is posted to the credit card or similar accountautomatically instead of resulting in a negative balance for the accountin low cash mode.

In some embodiments, the financial institution may provide customers theoption to draw on funds located in an alternative account for atransaction when an account is in low cash mode or when the transactionwill result in the account entering low cash mode. In response to analert provided by the financial institution, the financial institutionmay provide the customer with the ability to select an alternativeaccount associated with the customer from which to draw funds for thetransaction. The alternative account may be a checking account, savingsaccount, line of credit, or any other account associated with thecustomer. Additionally or alternatively, the financial institution mayprovide the option for a customer to preselect an alternative accountassociated with the customer from which to automatically draw funds whenthe account is in low cash mode or when the transaction will result inthe account entering low cash mode.

FIGS. 2A-2D provide various embodiments of the present disclosure thatillustrate linking a first account 131 with a second account 132. Toenable transfers from first account 131 to second account 132, anaccount owner may send a request to connect and/or link first account131 with second account 132. The request may be sent from user device108 that is registered to an account owner, where the request may bereceived by one or more of financial institution 106 and third-partyservice provider 110. The request may include a request from firstaccount 131 to second account 132 via user device 108, seekingauthorization from the owner of second account 132 to provide access totransaction data, account details, and/or other information pertainingto second account 132. In some embodiments, the owner (or joint owner)of the first account and the second account are the same person. Therequest may be transmitted to a user device 108 registered with secondaccount 132 for the owner of second account 132 to review. The requestmay include details on information to be shared, authorization to do so,and legal waivers for sharing personal and account details with athird-party. In response, owner of second account 132 may authorize, viauser device 108 and graphical user interface 118, the request to linkfirst account 131 with second account 132. The authorization may be sentback to third-party service providers 110 and/or financial institution106, which will link accounts and enable information sharing betweenowners of first account 131 and second 132.

The ability to monitor transactions in first account 131 from secondaccount 132 enables the owner of second account 132 to verify certaindeposits, whether transferred cash and/or funds are maintained for aperiod of time, and to monitor and track savings (and transferred funds)in first account 131. In the present embodiment, automatic electronictransfers may be made from second account 132 to first account 131 basedon activity in first account 131. For example, when first account 131enters a low cash mode, or when an account balance in first account 131drops beneath a predetermined threshold value, electronic transfers maybe made from second account 132 to first account 131 automatically.Alternatively, electronic transfers may be made manually based on userinteraction via a graphical user interface. A predetermined thresholdvalue may be a static value (e.g. $25) or alternatively, may represent,a dynamic percentage value (e.g. a percentage value of a total accountbalance) that may change over time. In the present embodiment, the ownerof second account 132 may be provided information, including transactiondetails and periodic statements, related to activity in first account131. The owner of second account 132 may then verify that rules arebeing applied correctly and that transferred funds to first account 131are transferred and maintained according to preset rules governing thefunds transfer. Particular rules with respect to transfers will bediscussed below.

FIGS. 2A-2D show various implementations in which financial institution106, third-party service provider 110, and user device 108 may bearranged in system 100. In FIG. 2A, first account 131 and second account132 may be maintained within a common financial institution 106. Firstaccount 131 and second account 132 may have differing or overlappingaccount ownership. Third-party service provider 110 may be a third-partyentity acting as an information clearing house or intermediary betweenfinancial institution 106 and user device 108, retrieving certain datafrom financial institution 106 and selectively providing data to accountowners via one or more user devices 108. Consistent with this presentembodiment, financial institution 106 may present options to customerswith at least one account in low cash mode or when an account balance infirst account 131 (or second account 132) drops beneath a predeterminedthreshold value.

FIG. 16 illustrates an exemplary flow chart for managing a financialaccount in low cash mode, consistent with disclosed embodiments. At step1602, financial institution 106 may provide an interface to a user, suchas via a user device 108 registered with a first account. User interfacemay be any of a dashboard or a window, and may include messages, icons,and or buttons for selection by a user.

At step 1604, financial institution 106 may transmit a notification to auser when the first account is deemed to be in a low-cash mode statebased on a balance in the first account, as disclosed herein. In someembodiments, the first account is deemed to be in the low-cash modestate when the first account balance is less than or equal to apredetermined percentage of a total amount of funds stored in the firstaccount.

At step 1606, financial institution 106 may display, when the firstaccount balance is less than a threshold value, an option to transferfunds into the first account. Financial institution 106 may determine,before transferring funds, that the second account has sufficient fundsto transfer the desired amount of funds to the first account withoutresulting in a negative account balance in the second account.

At step 1608, financial institution 106 may receive, via the interface,a selection of the option for the transfer request to connect the firstaccount with a second account. Financial institution 106 may requestauthorization, prior to transferring the funds, to initiate the transferof funds from the second account to the first account. Financialinstitution 106 may include a stored amount identifier, an indication ofsufficient funds in the second account, and a request for authorizationto transfer the funds from the second account to the first account basedon the stored amount identifier. In some embodiments, financialinstitution 106 may determine that the second account has insufficientfunds to transfer funds to the first account, and notify, via theinterface, the user that funds has not been transferred from the secondaccount to the first account.

At step 1610, financial institution 106 may transfer funds, based on therequest, from the second account to the first account. Financialinstitution 106 may store a date identifier associated with thetransferred cash, the date identifier indicating a deposit date fortransfer into the first account. Financial institution 106 may provide,via an interface accessible via a user device registered with the secondaccount, a fee indication specifying a fee associated with the transferrequest from the second account. Financial institution 106 may providevia an interface accessible via a user device registered with the secondaccount, a notification indicating the amount of funds transferred fromthe second account to the first account.

At step 1612, financial institution 106 may transmit a notification, viathe interface, to the user that funds have been transferred from thesecond account to the first account. At step 1614, financial institution106 may transmit an additional notification, via the interface, to theuser that the first account is not longer deemed to be in the low-cashmode state based on the new first account balance. Other notificationsnot shown, and consistent with this disclosure, may be contemplated.

System for Disabling Features

Consistent with disclosed embodiments, the financial institution mayprovide the option for a customer to disable some or all functionalityof an application on a mobile device. The financial institution maypresent this option when a customer indicates via phone call, webinterface, or visit to a branch location that a mobile device associatedwith the customer has been lost, misplaced, or stolen.

FIGS. 10A-10C illustrate exemplary graphical user interfaces having afirst disabled dashboard embodiment, consistent with disclosedembodiments. FIG. 10A illustrates an exemplary graphical user interfacehaving a dashboard embodiment for extra time, consistent with disclosedembodiments. At 1006, there is a display of time remaining to bring theaccount balance to at least $0.00 before the user is charged a negativebalance fee. Other sections of the interface 1002 may be disabledincluding sections pertaining to Virtual Wallet spread 1004, smart lock1008, payment control 1010, and funding options 1012. In someembodiments, financial institution may provide the option for a customerto disable some or all functionality of an application on a mobiledevice 108 (as shown in FIGS. 10A-10C). Financial institution maypresent this option when a customer indicates via phone call, webinterface, or visit to a branch location that a mobile device associatedwith the customer has been lost, misplaced, or stolen or based on otherpermissions/restrictions (such as parental controls).

At FIGS. 10B-10C, all sections (also referred to as subsections) ofinterfaces 1020, 1034 may be disabled with the exception of an extratime status 1024 which illustrates extra time item due 1026. Message1028 may state to a user “You'll need to deposit $90 by 12/3/19 to avoidpotential overdraft fees. You can only purchase extra time once pertransaction.” A close button may be displayed at 1020 and to make adeposit at 1032. At 1036, if a user's balance is not above $75 by adate, a user may be charged an overdraft fee.

System for Displaying a Grace Period

FIG. 4C illustrates an exemplary graphical user interface 424 forproviding an extra time remaining alert 426 to a customer, consistentwith disclosed embodiments. Consistent with present embodiments,financial institution 106 may display, either by providing an alert 426or via an interface 424 such as an application on a mobile device, aspecified amount of time representing a grace period within which thecustomer must cure a negative balance without the financial institutionassessing an associated negative balance fee. Such a feature may bedesirable for customers who struggle to manage their money or meetdeadlines regularly. In some embodiments the financial institution maydisplay a second specified amount of time remaining representing asecond grace period before the financial institution assesses anadditional negative balance fee when the customer failed to cure anegative balance within a previous grace period.

As shown in FIG. 4C, an extra time of “38 Hrs., 52 Min.” is displayed asa message 426 and allotted to the user as “time remaining to bring youraccount balance to at least $0.00 before you're charged a dailyoverdraft fee.” Message 426 additionally informs the user that he is“currently avoiding $20 in daily overdraft fees.” As in FIG. 4B, nextbutton 420 and skip button 422 may also enable a user to take a nextstep in the process of reviewing grace period or extra time optionsand/or skip the process of reviewing grace period options entirely.

System for Automatic Reminder Notifications

Consistent with the present embodiment, the financial institution mayprovide a notification to a customer during a grace period as a reminderto cure the negative balance. The financial institution may provide thenotifications to the customer at predetermined times. The times may bepredetermined by the financial institution or set by the customer. Thetimes may relate to the amount of time remaining to cure the negativebalance or the amount of time the balance has been negative. Thefinancial institution may provide notifications such as a pushnotification on a mobile device associated with the customer, an SMSnotification, an email notification, a voice call, a notificationthrough a social media account associated with the customer, or anyother notification intended to reach the customer.

System for Personalized Grace Periods

Consistent with the present embodiment, financial institution may alsopersonalize a grace period for individual customers based oncharacteristics associated with the customer. In one embodiment, thefinancial institution may determine the length of a grace period basedon the overdraft amount. For example, the financial institution maydetermine a shorter grace period for a small overdraft amount whiledetermining a longer grace period for a larger overdraft amount. Inanother example, the financial institution may determine a longer graceperiod for a small overdraft amount while determining a shorter graceperiod for a larger overdraft amount.

In another embodiment, financial institution may determine the length ofa grace period based on historical account data. The financialinstitution may determine a longer grace period if the historicalaccount data indicates that the account balance consistently remainsabove a predetermine threshold.

In another embodiment, financial institution may determine the length ofa grace period based on a customer's status with the financialinstitution. Financial institution 106 may determine longer a graceperiod for a customer in good standing with the financial institution.Financial institution 106 may also consider factors such as debit carduse, average balance, direct deposit amounts, timing of regularlyoccurring or historical transactions, or any other indicator of highactivity/volume with the financial institution when the financialinstitution determines if a customer is in good standing.

In another embodiment, financial institution may determine the length ofa grace period based on a customer's actions within the grace period.For example, financial institution 106, may determine to increase thelength of a grace period if the customer takes action to cure a negativebalance within a grace period but does not fully cure a negativebalance.

In another embodiment, financial institution may determine a fixedamount of time to be used as a grace period before an account balance isnegative. The fixed amount of time may be available for use by acustomer throughout a time period such as a month. The fixed amount oftime the financial institution determines as a grace period could thenbe instituted by the customer when an account has a negative balance.Financial institution would then refrain from assessing a negativebalance fee while grace period remains. When the grace period runs out,if the customer has not cured the negative balance, then the financialinstitution may assess a negative balance fee. If the customer cures thenegative balance before the grace period ends, then the financialinstitution may refrain from assessing a negative balance fee and theremaining grace period time may be remain available for use by thecustomer. The grace period may run during single instance of a negativeaccount balance or across multiple instances of negative account balanceby the customer within the time period.

In another embodiment, financial institution may determine a fixedamount of time to be used as a grace period based on historical dataassociated with a customer. Financial institution may determine the timeto be used by the customer as a grace period, for example, based on anumber of historical occurrences of a negative balance. In oneembodiment, the fixed amount of time to be used as a grace period isshorter when the customer has historical occurrences of a negativebalance. In another example, the fixed amount of time to be used as agrace period is longer when the customer has greater amounts of timebetween historical occurrences of a negative balance.

In another embodiment, financial institution may determine a fixedamount of time to be used as a grace period on a reoccurring basis forexample, monthly or annually. Financial institution may further allowtime allocated as a grace period to be saved, compiled, accumulated, orcarried over so that the customer continues to build a reserve of timeto be used as a grace period when an account balance is negative.However, financial institution may set a maximum amount of time to besaved, compiled, accumulated, or carried over as a grace period. Thefinancial institution may also implement other measures to limit theaccumulation of total grace period. For example, the time allotted as agrace period may expire if unused for length of time (such as one year).

In another embodiment, financial institution may allocate a fixed amountof time to be used as a grace period as an incentive. The incentive maybe given by the financial institution periodically, such as on theanniversary of the customer's relationship with the financialinstitution or may be included as an incentive within a package when acustomer purchases a product from financial institution. Additionally oralternatively, the time to be used as a grace period may be given as anincentive for referrals by a customer, rewarding the customer and a newcustomer invited by the customer with time to be used as a grace periodwhen the new customer opens an account with financial institution basedon an invitation from the customer. In another embodiment, financialinstitution may offer to sell more time to be used as a grace period tothe customer. Financial institution may allow the customer to purchaseadditional grace period time.

FIGS. 10A-10C illustrate exemplary graphical user interfaces having afirst disabled dashboard embodiment, consistent with disclosedembodiments. FIG. 10A illustrates an exemplary graphical user interface1002 having a dashboard embodiment for extra time, consistent withdisclosed embodiments. At 1006, there is a display of time remaining tobring the account balance to at least $0.00 before the user is charged anegative balance fee. Other sections of the interface 1002 may bedisabled including sections pertaining to Virtual Wallet spread 1004,smart lock 1008, payment control 1010, and funding options 1012. In someembodiments, financial institution may provide the option for a customerto disable some or all functionality of an application on a mobiledevice 108 (as shown in FIGS. 10A-10C). Financial institution maypresent this option when a customer indicates via phone call, webinterface, or visit to a branch location that a mobile device associatedwith the customer has been lost, misplaced, or stolen or based on otherpermissions/restrictions (such as parental controls).

FIG. 12 illustrates an exemplary graphical user interface for anapplication enabling payment control, consistent with disclosedembodiments. At graphical user interface 1202, a bank application forpayment control is shown having one or more subsections. At 1204, atitle of the application is displayed to the user. At 1206, a title of atransaction in question, in particular, check #125, may be displayed toa user with the associated amount. At 1208, a message may be displayedto a user as part of the application indicating that this transactionwill result in the account going negative and the user being charged anegative balance fee. At 1210, another message may explain the optionsavailable to a user. For example, at 1212, an option may be presented toa user to select the extra time option for this transaction.” At 1212A,1 Day may be selected as an extension with no associated cost. At 12B,an extension fee may be $2.00. At 1212C, an extension fee may be 3dollars. At 1212D, an extension fee may be 4 dollars. At 1212E, anextension fee may be 5 dollars. At 1214, a message may be provided to auser saying “Great we'll waive any potential fees on this transactionuntil 11/22” if an extension to 11/22 is selected by a user. At 1216, ifa user's account balance is positive on 11/22, no negative balance feewill be charged to the user. Conversely, if a user's account balance isstill negative, a banking application may charge the user a negativebalance fee of $20. At 1218, a user may click confirm to confirm anextension selection made.

FIG. 29 illustrates an exemplary flow chart for determining apersonalized grace period. At step 2902, financial institution 106 mayassociate a customer with an account. At step 2904, financialinstitution 106 may determine an account balance of the account. At step2906, financial institution 106 may provide a notification to thecustomer, as disclosed herein. At step 2908, financial institution maydetermine a personalized grace period, as disclosed herein. At step2910, financial institution may display the personalized grace period tothe customer.

System for Customized Reminder Notifications

In some embodiments, financial institution may present an option to thecustomer to allow the customer to dynamically set reminders within aninterface related to the financial institution so that the financialinstitution provides notifications to the customer reminding thecustomer to cure a negative account balance. Financial institution maysuggest time or increments for the reminder notifications. Financialinstitution may also permit customers to select reminders that areregularly occurring or persistent until the negative account balance iscured. Financial institution may further permit customers to select thetiming, time increments, consistency, or manner of remindernotifications.

System for Integration with PNC Virtual Wallet Calendar

In other embodiments, financial institution may provide the customerwith an option to view past, present, and future transactions on acalendar interface, for example the PNC Virtual Wallet Calendar. When anaccount enters low cash mode, the financial institution may providecustomers with the option to allow the financial institution toautomatically reschedule payments in order to prevent or cure a negativebalance. The financial institution may automatically rescheduletransactions by applying machine learning or artificial intelligencealgorithms to the calendared transactions.

System for Time Period-Based Negative Balance Fees

In some embodiments, the financial institution may provide a negativebalance fee as a substitute for a transactional fee when a customeraccount has insufficient funds. For example, the financial institutionmay provide the customer with the option of electing to pay a flat feefor every predetermined period of time in which the customer's accounthas a negative balance. In some embodiments the period of time is notpredetermined or may be dynamically adjusted to suit the customer basedon the customer's data or the customer account's historical data.

System for Recommendations Based on Scheduled Payments

Consistent with disclosed embodiments, the financial institution mayprovide a notification to a customer that a pending, scheduled, oranticipated purchase or transaction will result in a negative accountbalance before the purchase or transaction is made. For example, afinancial institution may notify a customer that a transactionassociated with an item placed in a virtual shopping cart while visitingan online merchant would result in a negative balance. In anotherembodiment the financial institution may use historical data associatedwith a customer to predict and notify a customer that an anticipatedtransaction will result in a negative balance. The financial institutionmay further anticipate transactions based on the time of the day, month,or year; a geographic location associated with a merchant; a geographiclocation associated with the customer; or other indicators associatedwith the customer and spending an amount greater than a current balance.

System for Maintaining a Minimum Threshold Value

In some embodiments, the financial institution may provide the customeran option of setting a low balance threshold. The low balance thresholdrepresents a maximum negative balance after the customer account enterslow cash mode. In electing to set a low balance threshold, the customercan prevent negative balances from decreasing beyond a negative amountset as the negative balance threshold. This provides the customer withpeace of mind that a negative balance will not exceed the customer'sability repay and also has the benefit of assisting the financialinstitution in assessing a financial risk profile associated with thecustomer. The low balance threshold may include providing the customerwith the ability to selectively choose one or more scheduled paymentsfor processing. Once the customer indicates that selection of scheduledpayments for processing is complete, the financial institution mayrender remaining scheduled payments unactionable. Unactionable paymentscannot be cancelled or modified by a customer but may be cancelled ormodified by the financial institution.

The low balance threshold may be dynamic and automatically set as afunction of various factors, such as the customer's age, income, creditscore, financial history, or other factors relevant to the customer'slikelihood of repaying a negative balance. In some embodiments, the lowbalance threshold is set by an agreement between the customer and thefinancial institution. The low balance threshold may also be set by thefinancial institution, allowing a customer to choose among scheduledpayments for processing but preventing the customer from changing thelow balance threshold amount.

In some embodiments, the financial institution may provide the customeran option of setting a low balance threshold. The low balance thresholdrepresents a maximum negative balance after the customer account enterslow cash mode. In electing to set a low balance threshold, the customercan prevent negative balances from decreasing beyond a negative amountset as the negative balance threshold. This provides the customer withpeace of mind that a negative balance will not exceed the customer'sability repay and also has the benefit of assisting the financialinstitution in assessing a financial risk profile associated with thecustomer. The low balance threshold may include providing the customerwith the ability to selectively choose one or more scheduled paymentsfor processing. Once the customer indicates that selection of scheduledpayments for processing is complete, the financial institution mayrender remaining scheduled payments unactionable. Unactionable paymentscannot be cancelled or modified by a customer but may be cancelled ormodified by the financial institution.

The low balance threshold may be dynamic and automatically set as afunction of various factors, such as the customer's age, income, creditscore, financial history, or other factors relevant to the customer'slikelihood of repaying a negative balance. In some embodiments, the lowbalance threshold is set by an agreement between the customer and thefinancial institution. The low balance threshold may also be set by thefinancial institution, allowing a customer to choose among scheduledpayments for processing but preventing the customer from changing thelow balance threshold amount.

FIGS. 11A-11D illustrates exemplary graphical user interfaces for lowcash mode customization and configurations, consistent with disclosedembodiments. FIG. 5A illustrates an exemplary graphical user interfacefor setting a low cash mode threshold, consistent with disclosedembodiments. As shown in FIG. 5A, a user may configure or customize alow cash mode by setting a low cash threshold. When a user's account isbelow their threshold, the user may be able to control individual checksand automatic checks are paid or rejected. As shown in FIG. 5A, a usermay enable their low cash mode controls 506 when their account balancefalls beneath $10, $25, $50, $100, or a custom amount. Back 508 andContinue 510 buttons may be provided for users to navigate betweenscreens to allow for further configuration or customization of low cashmode preferences or properties. Additionally or alternatively, the usermay select to automatically enable low cash mode based on adetermination by the financial institution (not show). The financialinstitution would then determine when the account enters low cash modeas discussed herein.

FIG. 5D illustrates an exemplary graphical user interface for setting aplurality of threshold values for paying or rejecting payments,consistent with disclosed embodiments. As shown in FIG. 5D, a user maybe able to activate low cash mode controls when their account balance isat or below a certain value (e.g. $50). The user may be able to selectfrom a plurality of different threshold values or enter a customthreshold value. The user may be able to choose if the account willdefault to pay or reject payments when low cash mode activates and mayalso choose if the account will default to pay or reject payments whenlow cash mode activates. The user may select a monetary value for atwhich their account will default to pay or reject payments when low cashmode activates. A confirm button 536 may be provided for a user toaccept the and save the selected low cash mode threshold settings.

FIG. 30 illustrates an exemplary flow chart for managing a financialaccount. At step 3002, financial institution 106 may associate acustomer with an account at financial institution 106. At step 3004,financial institution 106 may receive a low balance threshold asdetermined by financial institution 106 or from a customer. At step3006, financial institution 106 may determine an account balance of theaccount.

At step 3008, financial institution 106 may determine, based on theaccount balance and low balance threshold, whether the account is lessthan the low balance threshold. At step 3010, financial institution 106may provide a notification to the customer, as disclosed herein. At step3012, financial institution 106 may present options to manage theaccount while the account balance is less than the low balancethreshold.

System for Predictive Cash Flow

Consistent with disclosed embodiments, the financial institution mayapply artificial intelligence or machine learning algorithms tohistorical data stored in a data platform and associated with a customeror account in order to learn and predict transactions and spendingtendencies. The historical data may additionally include data availablethrough the customer's social media account(s). Financial institution106 may further provide notifications or recommendations based on thepredicted transactions or spending tendencies.

In some embodiments, the financial institution may provide the customerwith a predictive cash flow feature. The predictive cash flow featuremay use one or more of the customer's financial history, the customeraccount history, and aggregated data from other customers and customeraccounts to create one or more predictions. The one or more predictionsmay include time periods or amounts related to a customer's financialstatus, and may include time periods when a customer is more likely toenter low cash mode. The predictive cash flow feature may, by way ofillustrative example, analyze a customer's financial history anddetermine patterns corresponding to when the customer's account receivesdeposits or when the customer makes expenditures. Through this analysis,the predictive cash flow feature may determine probabilities for acustomer account entering low cash mode and, when a probability iswithin certain range, notify a customer of a prediction. The predictivecash flow feature may similarly provide the customer with a predictioncorresponding to a high likelihood of a low customer account balance ornegative balance.

In some embodiments, the predictive cash flow feature incorporatesmachine learning to create more accurate predictions. For example, thefinancial institution may apply machine learning or artificialintelligence algorithms to evaluate historical predictions and theiraccuracy in comparison to actual customer account status. The predictivecash flow feature may then adjust data inputs used for predictions thatwere historically less accurate and leave unmodified data inputs usedfor predictions that were historically accurate. In addition, thepredictive cash flow feature may create predictions for the purpose ofevaluating and enhancing future predictions without sending thepredictions to a customer. This enables the predictive cash flow featureto continually improve the accuracy of predictions while providing acustomer with the most accurate predictions.

In some embodiments the predictive cash flow feature incorporates datareceived and stored by the financial institution as well as datareceived from third parties. Data received from third parties may enablethe financial institution to create more holistic and accuratepredictions by incorporating more data into its analysis. Data includedin the predictive cash flow feature may include non-financial data, suchas calendar data, weather data, or other types of data associated withor correlating to financial behavior.

In some embodiments, the predictive cash flow feature allows a customerthe ability to manually add payments to be analyzing or given greaterweight in generating predicative cash flows.

FIGS. 7A-7C illustrate exemplary graphical user interfaces forpredicting a low cash mode and related expenses, consistent withdisclosed embodiments. FIG. 7A illustrates an exemplary graphical userinterface 702 for notifying a customer that an account associated withthe customer may enter low cash mode in a future time period, consistentwith disclosed embodiments. As shown in FIG. 7A, an intelligent alert706 indicates “Low Cash Mode ahead” and “We predict your account x2958could enter low cash mode in the next 3 days. Review your options.” FIG.7B illustrates an exemplary graphical user interface 708 for displayinga predicted cash flow forecast 710, consistent with disclosedembodiments. As shown in FIG. 7B, a predictive cash flow forecast 710may display a line graph indicating a prediction of cash flow over aperiod of time. A message 712 may also be displayed with a detailssection 714 for the user's reference to explain the predicted cash flow.A user may be able to manage and review scheduled and predicted payments716 and may also list scheduled out amounts 718 and predictedreoccurring expenses 720. Additionally, funding options 722 may allowfor funding a user's account with the following options. The options mayinclude making a transfer 724 and making a deposit 726. The user maythen confirm and return to the account 730.

FIG. 7C illustrates an exemplary graphical user interface 732 forpredicting expenses, consistent with disclosed embodiments. As shown inFIG. 7C, predictive expenses may be displayed to the user in graphicaluser interface 732. The graphical user interface 732 may includeexpenses identified from past user activity. The user may be able tounselect an expense if the user does not want to use the expectedtransaction to predict a future balance. As shown, expected activity 738may list expected expenses 740, 742 which are shown as “Verizon Fios”and “Netflix” expenses. The user may then confirm and return to theaccount 744.

FIG. 31 illustrates an exemplary process for predicting cash flow. Atstep 3102, financial institution 106 may associate a customer with anaccount at financial institution 106. At step 3104, financialinstitution 106 may store financial history data associated with thecustomer and/or the account. At step 3106, financial institution 106 maystore account history data associated with the customer and/or theaccount. At step 3108, financial institution 106 may store aggregateddata. At step 3110, financial institution 106 may access non-financialdata.

At step 3112, financial institution 106 may analyze by machine learningthe financial history data, the account history data, the non-financialdata and the aggregated data. At step 3114, financial institution 106may determine a future account balance of the account based on theanalysis performed in step 3114. At step 3116, financial institution 106may determine, based on the future account balance, whether the firstaccount will enter a low-cash mode state, as disclosed herein. At step3118, financial institution may determine a danger time period for thecustomer or the account, as disclosed herein.

System for Communication Through Social Media

In some embodiments, the financial institution may urge or permitcustomers to link financial accounts with social media accounts. Thelink between accounts may provide financial institution with access toinformation gathered by the social media account and associatedapplications. The link may also provide another channel for financialinstitution to send alerts or messages to a customer. For example, acustomer could receive a message via a social network instant or directmessage that the account has entered low cash mode.

Additionally or alternatively, the financial institution may provide acustomer with the option to associate a social media account associatedwith the customer with a financial account. The financial institutionmay then interact with the customer using the notifications andinfrastructure provided by the social media platform. For example, thefinancial institution may provide a notification that an accountassociated with a user has entered low cash mode using FacebookMessenger or Twitter Direct Message. The financial institution may alsoaccess or analyze data associated with a customer's social mediaprofile, presence, usage, activity, connections, or other social mediadata.

FIG. 22 illustrates an exemplary flow chart for providing notificationto a customer. At step 2202, financial institution 106 may associate acustomer with an account at the financial institution. At step 2204,financial institution 106 may associate the customer with a social mediaaccount. At step 2206, financial institution 106 may present an optionvia the customer interface with financial institution 106 or via thesocial media platform for the customer to grant financial institution106 permission to link the account associated with the customer atfinancial institution 106 with the social media account associated withthe customer.

At step 2208, financial institution 106 may receive permission to linkthe account at financial institution 106 associated with the customerwith the social media account associated with the customer. At step2210, financial institution may link the account at financialinstitution 106 associated with the customer with the social mediaaccount associated with the customer.

At step 2212, financial institution 106 may determine an account balanceof the account. At step 2214, financial institution 106 may determine,based on the account balance, whether the account is deemed to be in alow-cash mode state, as disclosed herein. At step 2216, if the accountis deemed to be in a low-cash mode state, financial institution 106 mayprovide a notification to the customer that the account is deemed to bein a low-cash mode state via the social media account associated withthe customer.

System for Geolocation Based Alerts

In some embodiments, financial institution may offer customers theoption to designate payments based on a user's location (as discussedherein). A customer may, for example, use a mobile device that isassociated with a customer account. The mobile device may have a GPS orbe otherwise configured with location services to determine the locationof the mobile device. When the mobile device determines that thelocation of the mobile device is within a predetermined distance from amerchant while the customer's account is in low cash mode, the mobiledevice may provide a notification to the customer and provide thecustomer with the option of designating the merchant for paymentprocessing during low cash mode.

In some embodiments, financial institution may offer a geolocation alertservice. The geolocation alert service includes a customer carrying amobile device with a global positioning system or other locationservices. The mobile device may determine a location of the mobiledevice and communicate the location to the financial institution or to amobile application associated with the financial institution. Thefinancial institution, either through its own servers or through themobile application, may determine whether the location is associatedwith a merchant and whether the customer account associated with themobile device is low cash mode. If the financial institution determinesthat the customer account is in low cash mode and the location isassociated with a merchant, the financial institution may notify thecustomer that the customer account is in low cash mode. The financialinstitution may provide such notification by, for example, sending atext message to a phone number associated with the customer account,sending an email to an email address associated with the customeraccount, sending a push notification to the mobile device via the mobileapplication, and/or any other notification disclosed herein.

In some embodiments, the geolocation alert service may similarly notifythe customer when the customer account is within a certain range of thethreshold for entering low cash mode. For example, the financialinstitution may notify the customer that the customer's account iswithin a specified dollar amount of entering low cash mode when thecustomer carries their mobile device to a merchant.

In some embodiments, the financial institution may notify more than onecustomer associated with a customer account when the customer account isin low cash mode and the location is associated with a merchant. Forexample, when one of multiple customers associated with an accountenters a location associated with a merchant, the financial institutionmay notify all associated customers that the customer account is in lowcash mode and that one of the customers is entering a merchant. This isparticularly useful in joint accounts where one joint account holderwould otherwise be able to spend while the customer account is in lowcash mode without the knowledge of the other joint account holder. Insome embodiments, the financial institution may allow customers to setparental controls or designate one or more controlling agents so thatnotifications are sent to one or more parents or controlling agents.

In some embodiments, the geolocation alert service may be enabled basedon predicted danger conditions. One or more customers, parents, orcontrolling agents may, for example, may determine a danger conditionunder which they will be notified through the geolocation alert service.The danger condition may be any condition that is predicted to result ina high financial risk or a high risk of a customer account entering lowcash mode. For example, the danger condition may be the mobile deviceentering a location associated with a merchant known for sellinghigh-value products. Under such a danger condition, the geolocationalert service would assist customers with taking informed andfinancially responsible actions by notifying them when they could end upspending a high amount of money and thereby cause a customer account toenter low cash mode.

Other examples of danger conditions include merchants determined to bedisreputable, merchants with high interest rates, merchants at which thecustomer account has previously entered low cash mode, merchants atwhich other customer accounts have entered low cash mode, a time or timeperiod associated with impulsive buying or other customer accountsentering low cash mode, and a time or time period associated with acustomer's regular income receipt.

In some embodiments, the financial institution may request or requirethe consent of the customer to enable the geolocation alert service. Thefinancial institution may, by way of example, request permission from acustomer to enable the geolocation alert service when a customerinstalls the mobile application on a mobile device, or the financialinstitution may require the consent of the customer to enable thegeolocation alert service and accept various terms upon installation ofthe mobile application.

FIGS. 15A-15B illustrates exemplary graphical user interfaces forspending control and automatic locking, consistent with disclosedembodiments. User interface 1502 illustrates a bank smart lock userinterface with simplified spending control 1504. At 1506, a message ispresented explaining the available features of simplified spendingcontrol to a user. At 1510, there is a button to display the next screenor message. At 1512, there is a button to dismiss the message and returnto a previous graphical user interface 1512. At user interface 1514illustrated in FIG. 15B, there is intelligent, automatic locking 1516.At 1518, a message is presented explaining the available features ofintelligent, automatic locking to a user. At 1520, an icon indicatingthe intelligent, automatic locking 1516.

FIGS. 14A-14B illustrates exemplary graphical user interfaces for a bankapplication enabling a smart geolocation feature, consistent withdisclosed embodiments. At FIG. 14A, manage locations 1420 userinterface, frequent locations 1422 may list locations frequentlyvisited, such as a Giant Eagle in Cranberry, PA. At 1424, recommendlocations may be present, for example, at grocery stores. At 1426, theuser may manually add a location. At 1428, a map may be present to showlocations of grocery stores. At 1430, the user may add a selectedlocation. As shown in FIG. 14B, user interface 1432 may notify the userat 1434 that the user is near a frequent location and that the accountis currently smart locked to prevent transactions from being processedand that the user must sign in to make changes.

FIGS. 15C-15D illustrate exemplary graphical user interfaces forexplaining danger day features and geolocation control features,consistent with disclosed embodiments.

FIG. 32 illustrates an exemplary flowchart for preventing a negativeaccount balance. At step 3202, financial institution 106 may associate afirst customer with an account at financial institution 106. At step3204, financial institution 106 may associate a second customer with theaccount at financial institution 106. At step 3206, financialinstitution 106 may associate the first customer with a first mobiledevice. At step 3208, financial institution 106 may associate the secondcustomer with a second mobile device.

At step 3210, financial institution 106 may determine an account balanceof the account. At step 3212, financial institution 106 may determine,based on the account balance, whether the account is deemed to be in alow-cash mode state, as disclosed herein.

At step 3214, financial institution may determine the location of thefirst customer via the first device. At step 3216, financial institutionmay determine if the location of the first customer is associated with amerchant. At step 3218, financial institution may provide a notificationto the first customer, the second customer, or both, as disclosedherein.

FIG. 33 illustrates an exemplary process for preventing a negativebalance. At step 3302, financial institution 106 may associate a firstcustomer with an account at financial institution. At step 3304,financial institution 106 may associate multiple other customers withthe account at financial institution 106. At step 3306, financialinstitution 106 may associated the first customer with a first mobiledevice. At step 3308, financial institution 106 may store financialhistory data associated with the customer and/or the account. At step3310, financial institution 106 may store account history dataassociated with the customer, the multiple customers, and/or theaccount. At step 3312, financial institution 106 may store aggregateddata. At step 3314, financial institution 106 may access non-financialdata.

At step 3316, financial institution 106 may analyze by machine learningthe financial history data, the account history data, the aggregateddata and the non-financial data. At step 3318, financial institution 106may determine a future account balance of the account based on theanalysis performed in step 3316. At step 3320, financial institution 106may determine, based on the future account balance, whether the firstaccount will enter a low-cash mode state, as disclosed herein.

At step 3322, financial institution may determine the location of thefirst customer via the first device. At step 32163324 financialinstitution may determine if the location of the first customer isassociated with a merchant. At step 3326, financial institution mayprovide a notification to the first customer, the multiple customers, orboth, as disclosed herein.

FIG. 34 illustrates an exemplary process for preventing a negativebalance. At step 3402, financial institution may associate a firstcustomer with an account at financial institution 106. At step 3404,financial institution 106 may associate multiple other customers withthe account at financial institution 106. At step 3406, financialinstitution 106 may associate the first customer with a first mobiledevice. At step 3408, financial institution 106 may store financialhistory data associated with the customer and/or the account. At step3410, financial institution 106 may store account history dataassociated with the customer, the multiple customers, and/or theaccount. At step 3412, financial institution 106 may store aggregateddata. At step 3414, financial institution 106 may access non-financialdata.

At step 3416, financial institution 106 may analyze by machine learningthe financial history data, the account history data, the aggregateddata and the non-financial data. At step 3418, financial institution 106may determine a future account balance of the account based on theanalysis performed in step 3416. At step 3420, financial institution 106may determine, based on the future account balance, whether the firstaccount will enter a low-cash mode state, as disclosed herein.

At step 3422, financial institution may determine the location of thefirst customer via the first device. At step 3424, financial institutionmay determine a danger condition. At step 3326, financial institutionmay provide a notification to the first customer, the multiplecustomers, or both, as disclosed herein.

Systems for Exemptions from Low-Cash Mode

In some embodiments, financial institution may provide the customer withone or more low cash mode payment recommendations (such as groceryrecommendations as discussed herein). When additional payments are madeby a customer whose account is in low cash mode, financial institutionmay use customer data, customer account data, financial institutiondata, third party data, or a combination thereof to determine an optimalway for the customer to schedule payments. For example, the financialinstitution may analyze the scheduled payments for the customer accountand a fee schedule associated with the customer account and recommendwhich scheduled payments the customer should pay in order to minimizeincurring fees. Low cash mode payment recommendations benefit thefinancial institution by providing customers with advice that maymitigate their risk profile to the financial institution and byincreasing customer satisfaction with the financial institution. Lowcash mode payment recommendations benefits customers by empowering themwith information and flexibility while aiding their financial decisionswhen funds are insufficient and financial advice is needed most.

In some embodiments, financial institution may offer customers variousoptions to process designated transactions for processing even while inlow cash mode. For example, financial institution may offer customersthe option to designate payments for processing that are made at agrocery store (as discussed above) even while in low cash mode. Thefinancial institution may offer customers options to designateparticular merchants or types of payments prior to or upon thecustomer's account entering low cash mode. Financial institution mayalso offer customers the option to designate particular merchants ortypes of payment while the customer's account is in low cash mode.

In some embodiments, financial institution may provide the customer witha list of merchants and the customer may select one or more merchantsfrom the list. The financial institution will then process transactionsinitiated by the selected merchants while the associated account is inlow cash mode. In some embodiments, financial institution provides theuser with a list of types of payments and the user selects one or moretypes of payment from the list. The financial institution will thenprocess transactions corresponding to the selected payments while theassociated account in in low cash mode. The types of payment mayinclude, for example, payment categories. The financial institution mayobtain payment categories from a third party or determine such paymentcategories using financial data and historical financial transactiondata associated with a particular merchant, payment amount, or time ofpayment.

Systems Providing User Interface

In some embodiments, as used herein, micro-applications may be used toimplement a low cash mode of operation as displayed on a graphical userinterface or webpage (as discussed above) or on a mobile device (asdiscussed below). For example, a low cash mode may be used to refer towhen an account balance in a financial account drops beneath apredetermined threshold value, and additionally, to options presented byfinancial service provider 110 (e.g. personal loan, transfer of fund,and the like) when financial service provider 110 determines that anaccount has insufficient funds to handle a transaction without resultingin a negative balance.

FIGS. 6-7 illustrate exemplary bank account webpages for use withapplications, consistent with disclosed embodiments. FIG. 3A illustratesa user interface that may exchange data to present a holistic andconsistent user banking experience, such as a banking account summarywebpage 302. Deposit accounts 308 and interest checking 310 and avirtual wallet 312 may be shown as part of a consistent user experience.Credit account 314 may also be shown as part of a consistent userexperience. Information message boxes 316 and 318 may also be displayedon banking account summary webpage 302. Message 316 such as “access yourmoney fast with bank express funds” and “learn how to get immediateaccess to your funds when depositing an approved check from your mobiledevice or at an ATM” may be part of the user banking experience. Othermessage 318 may include “Tips on how to spot a scam! Fraudsters mayattempt to steal your personal and financial information through emails,texts, and call,” and may be part of a user experience. Other links 320may be presented at the bottom of account summary webpage 302.

In some embodiments, balance data for each of the three deposit accounts322, 324 and for the credit account 326 may also be shown as part ofwebpage 302 as shown in FIG. 3B.

In some embodiments, a customer may be provided with a user interface.The user interface may provide the customer with a variety ofnotifications, such as notifications triggered when the customer'saccount enters or exits low cash mode as well as notifications providingeducation as to the features an options available for accounts in lowcash mode. The user interface may also be configured to display avariety of settings, including display settings, notification settings,customer account settings, and low cash mode settings. In addition todisplaying these settings, the user interface allows a user, which mayor may not be the customer, to adjust these settings. By displaying thesettings in an aesthetically pleasing and intuitive manner, a user mayfeel more informed and empowered to control their customer account andthe functionality of low cash mode. In some embodiments, the userinterface is customizable such that portions of the user interface maybe rearranged according to the needs or preferences of the user. In someembodiments, the customizability of the user interface is reduced topromote uniformity of user experience across a variety of users.

The user interface may be provided on a variety of devices, such asmobile devices, tablets, laptops, desktop computers, Automated TellerMachines (ATMs), or other devices. Furthermore, the user interface maybe provided for use by a single user or may be configured for use bymore than one user, such as a user interface configured to provideaccess to many users at a publicly accessible device.

In some embodiments, the user interface comprises one or more panels.Each panel may include text or images to provide a user with accountinformation, or provide a user with notifications regarding such accountinformation. The account information may include low cash modeinformation associated with a customer account, such as a balanceavailable to the user, current settings of low cash mode, fundingoptions, fund transfer information, fund deposit information, timeremaining until overdraft or other fees are incurred, overdraft or otherfees being avoided by the user's actions or settings over variousperiods of time, current payment control settings, and paymentsavailable for viewing by a user. In some embodiments, the accountinformation includes payment control information, such as protectedbalance, available balance, returned payments, payment schedules, andpayment decision deadlines.

When a user interacts with one or more panels (for example by tapping,swiping, clicking with a cursor, or otherwise performing an actionindicative of a user's choice), the user interface may change to includenew or additional information displayed through the interface or providea user with new or additional settings. For example, one panel mayinclude information regarding a balance available through low cash mode.When the user interacts with the panel, the user interface may change todisplay more detailed information regarding the available balance, suchas a transaction history or a detailed time stamp for when low cash modewas enabled. In some embodiments, one panel may include payment controlnotifications. When the user interacts with the panel, the userinterface may change to display payment control information, settings,and/or choices. Such payment control choices may include, for example,buttons enabling the user to select payments the user does not want paidusing the customer account.

FIGS. 10A-10E illustrate exemplary graphical user interfaces formanaging a financial account in a low cash mode, consistent withdisclosed embodiments. FIG. 4A illustrates an exemplary graphical userinterface 402 for managing a financial account in low cash mode,consistent with disclosed embodiments. As shown in FIG. 4A, graphicaluser interface 402 may include a home page that provides an overview ofoptions available to a user at user device 108, educating the user aboutlow cash mode. Graphical user interface 402 may include optionsincluding opting-into intelligent alerts 406, receiving automaticextensions of time 408, managing payment controls 410, and activating adebit cart smart lock 412. In present embodiments, intelligent alerts406 may communicate to a user when an account associated with the userenters low cash mode and when the user needs to take action related tothe account or a transaction. Automatic extra time 408 may allow a userto avoid overdraft fees and may provide a length of time (for example,48 hours) for a user to cure the negative account balance beforeincurring a negative balance fee. Payment controls 410 may allow a userto decide if individual checks as automatic payments are paid orrejected when in low cash mode. Debit card smart lock 412 may allow auser to choose to automatically lock their debit card to avoid spendingwhen their balance is low. Additionally or alternatively, a user mayactivate debit card smart lock 412 manually at any time. Other featuresmay be contemplated and included in a home page in order to allow a userto manager his or her financial account in low cash mode.

While some features relating services, technologies, and featuresoffered by a financial services provider have been described withrespect to the above embodiments, it should be understood that they arenot limited thereto, and that various other features may be included orfeatured. The accompanying figures are intended to provide exemplaryviews for purposes of explaining systems and methods described herein,and they are not intended to limit the scope of those features orinterfaces.

In some embodiments, some or all of the logic for the above-describedtechniques may be implemented as a computer program, as an application,or as a plug-in module or sub-component of another application. Thedescribed techniques may be varied and are not limited to the examplesor descriptions provided. In some examples applications may be developedfor download to mobile communications and computing systems, e.g.,laptops, mobile computers, tablet computers, smartphones, etc., beingmade available for download by the customer either directly from thedevice or through a website.

Moreover, while illustrative embodiments have been described herein, thescope thereof includes any and all embodiments having equivalentelements, modifications, omissions, combinations (e.g., of aspectsacross various embodiments), adaptations and/or alterations as would beappreciated by those in the art based on the present disclosure. Forexample, the number and orientation of components shown in the exemplarysystems may be modified. Further, with respect to the exemplary methodsillustrated in the attached drawings, the order and sequence of stepsmay be modified or combined, and/or steps may be added or deleted.

Thus, the foregoing description has been presented for purposes ofillustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations will beapparent to those skilled in the art from consideration of thespecification and practice of the disclosed embodiments. For example,while a financial institution may have been described herein as theentity managing and/or maintaining the financial accounts 130 andproviding the graphical user interface 118 for user device 108, it is tobe understood that, consistent with disclosed embodiments, anotherentity may provide such services in conjunction with or separate from afinancial institution. For example, third-party service provider 110 mayprovide some or all of the above-described functions.

The claims are to be interpreted broadly based on the language employedin the claims and not limited to examples described in the presentspecification. Accordingly, the examples presented herein are to beconstrued as non-exclusive. Further, the steps of the disclosed methodsmay be modified in any manner, including by reordering steps and/orinserting or deleting steps.

Furthermore, although aspects of the disclosed embodiments are describedas being associated with data stored in memory and other tangiblecomputer-readable storage mediums, one skilled in the art willappreciate that these aspects can also be stored on and executed frommany types of tangible computer-readable media, such as secondarystorage devices, like hard disks, floppy disks, or CD-ROM, or otherforms of RAM or ROM. Accordingly, the disclosed embodiments are notlimited to the above-described examples but, instead, are defined by theappended claims in light of their full scope of equivalents.

What is claimed is:
 1. A system for conveying real time information fromone or more computer servers to a computing device display and enablingreal time account controls responsive to the computing device userinterface, comprising: one or more computer servers; a network interfacethat connects the one or more computer servers to a plurality ofcomputing devices, wherein the plurality of computing devices have adownloaded mobile application; at least one memory storing instructions;and at least one processor configured to execute the instructions toperform operations comprising: authenticating, via an encrypted networkconnection over the network interface, a computing device of theplurality of computing devices with a computer server of the pluralityof computer servers; associating the computing device with at least oneaccount maintained in the computer server; associating the computingdevice with a unique identifier corresponding to the at least oneaccount; generating, in the downloaded mobile application on thecomputing device associated with the account, a user interface, whereinthe user interface comprises a plurality of rectangular dashboard panelsfor initiating operations associated with the account; initializing afirst dashboard panel comprising account settings or real time accountinformation specific to a first mode of operation and a second dashboardpanel comprising account settings or real time account informationspecific to a second mode of operation, wherein the first mode ofoperation corresponds to an account balance above a pre-determinedthreshold and the second mode of operation corresponds to an accountbalance below the pre-determined threshold; displaying, on the userinterface, in a vertical stack layout, the first dashboard panel and thesecond dashboard panel simultaneously, wherein the first dashboard paneloccupies an upper portion of the vertical stack layout and the seconddashboard panel occupies a lower portion of the vertical stack layout;receiving, via the network connection, account information based on theunique identifier corresponding to the account, wherein the accountinformation includes an account balance; determining that the accountbalance is negative; determining, based on the account balance, that theaccount is in the second mode of operation; responsive to thedetermination that the account is in the second mode of operation:disabling a debit card associated with the account; decliningtransactions directed to the account; disabling functionality associatedwith the first dashboard panel and specific to the first mode ofoperation via graying-out the appearance of the first dashboard panel;and enabling functionality associated with the second dashboard paneland specific to the second mode of operation, wherein the firstdashboard panel and the second dashboard panel remain visible in theuser interface while the account is in the second mode of operation;accessing, via the network, a first database associated with the accountto retrieve historical account data associated with the account;accessing, via the network, a second database associated with theaccount to retrieve non-financial data associated with the account;determining a negative balance fee to assess against the account basedon at least the historical account data and the non-financial data;determining a fixed period of time before applying the negative balancefee to the account; transmitting, to the computing device associatedwith the unique identifier, a first message for display in the firstdashboard panel while the account is in the second mode of operation,the first message comprising at least one of an indication that theaccount is in the second mode of operation, an indication of the accountbalance, or an option to unlock a debit card associated with theaccount; transmitting, to the computing device and based on the uniqueidentifier, a second message for display in the second dashboard panelwhile the account is in the second mode of operation, wherein the secondmessage comprises at least one of: an indication of the period of timebefore a negative balance fee is assessed, an indication of the negativebalance fee, or the option to make a deposit; following expiration ofthe fixed period of time, determining whether the account balance isnegative; and responsive to the determination that the account balanceis negative, applying the negative balance fee to the account.
 2. Thesystem of claim 1, wherein the determination of the negative balance feeis further based on an extent to which the account balance is negative.3. The system of claim 2, wherein the negative balance fee is higher forlarger negative amounts as compared to smaller negative amounts.
 4. Thesystem of claim 1, wherein the determination of the negative balance feeis determined based in part on a number of historical occurrences ofnegative account balances.
 5. The system of claim 4, wherein thenegative balance fee is directly proportional to the number ofhistorical occurrences of negative balances.
 6. The system of claim 1,wherein the at least one processor is configured to execute theinstructions to perform operations further comprising: determining aplurality of tiered negative balance fees, wherein each of the tierednegative balance fees corresponds to a range of negative balanceamounts; selecting one of the plurality of tiered negative balance feesto assess to the account, wherein the selection is further based on theextent to which the account balance is negative.
 7. The system of claim6, wherein the at least one processor is configured to select a highernegative balance fee of the plurality of tiered negative balance feesfor larger negative amounts as compared to smaller negative amounts. 8.The system of claim 6, wherein the selected negative balance fee of theplurality of tiered negative balance fees is zero.
 9. The system ofclaim 1, wherein the duration of the period of time before the negativebalance fee is assessed to the account is determined based on the amountof time since the account's last negative balance.
 10. The system ofclaim 9, wherein the duration of the period of time before the negativebalance fee is assessed to the account is directly proportional to theamount of time since the account's last negative balance.
 11. The systemof claim 1, wherein the duration of the period of time before thenegative balance fee is assessed to the account is determined based on ahistorical account balance.
 12. The system of claim 11, wherein theduration of the period of time before the negative balance fee isassessed to the account is longer when the historical account balance isconsistently above a predetermined threshold.
 13. The system of claim 1,wherein the duration of the period of time before the negative balancefee is assessed to the account is determined based on a number ofhistorical occurrences of negative account balance.
 14. The system ofclaim 13, wherein the duration of the period of time before the negativebalance fee is assessed to the account is shorter when the account hashistorical occurrences of a negative balance.
 15. The system of claim 1,wherein the duration of the period of time before the negative balancefee is assessed to the account is accrued from month-to-month.
 16. Thesystem of claim 1, wherein the second message further comprises anoption to purchase an additional duration of time before the negativebalance fee is assessed to the account.
 17. The system of claim 16,wherein the option to purchase an additional duration of time before thenegative balance fee is assessed to the account is presented once. 18.The system of claim 1, wherein the duration of the period of time beforethe negative balance fee is assessed to the account is automaticallyincreased responsive to an action toward curing the negative balancewithin the fixed period of time.
 19. The system of claim 18, wherein theaction comprises depositing funds into the account.
 20. The system ofclaim 18, wherein the action comprises rescheduling one or morepayments.
 21. The system of claim 1, wherein the at least one processoris configured to execute the instructions to perform operations furthercomprising: automatically rescheduling one or more payments to minimizea magnitude of a negative account balance during the fixed period oftime.
 22. The system of claim 1, wherein the at least one processor isconfigured to execute the instructions to perform operations furthercomprising: determining, after the negative balance fee is applied tothe account, whether the negative balance is cured; determining, afterthe negative balance fee is applied to the account and based on thepresent account balance, that the account is in the first mode ofoperation; responsive to the determination that the account is in thefirst mode of operation: disabling functionality associated with thesecond dashboard panel and specific to the second mode of operation; andenabling functionality associated with the first dashboard panel andspecific to the first mode of operation, wherein the first dashboardpanel and the second dashboard panel remain visible in the userinterface while the account is in the first mode of operation.
 23. Thesystem of claim 1, wherein the at least one processor is a processor ofthe computing device.
 24. The system of claim 2, wherein the at leastone processor is a processor of the computer server.